Hi, I did try it out with 3.7.0-SNAPSHOT but the outcome was the same. I'll put in a JIRA ticket and I'll provide details on how I was able to replicate the issue. I'll also post it on here.
cheers andy On Mon, Nov 30, 2020 at 7:59 PM Zoran Regvart <[email protected]> wrote: > > Hi Andy, > sounds like an issue we would not encounter when developing/running > integration tests. We have a number of issues (some of them have been > fixed) relating to streaming/push APIs with Salesforce. > > Perhaps if you find that the recent versions did not fix your issue > you could contribute the logic of your custom error handler. Sounds > like you've also arrived at a setup where you can reproduce and test > the fix. > > I'm guessing it could fit within the SubscriptionHelper class. > > zoran > > On Fri, Nov 27, 2020 at 4:14 AM Andy Stebbing <[email protected]> > wrote: > > > > Hi There, > > I'm using the salesforce component for receiving platform events and > > have been using it for a few months and is generally quite stable. > > > > My question is around the durability of the subscription, for normal > > network dropouts or timeouts etc, it handles it very well, but > > recently Salesforce have had some big outages in my org and it causes > > the subscription to stop working without re-subscribing again. > > > > I can replicate the issue locally, running my camel route so it > > initially subscribes to the events then I firewall block the > > Salesforce destination then i restart the route. It fails and then > > unsubscribes from the events and when i open the firewall it connects > > but never re-subscribes to the events again. Any new events from > > Salesforce are not consumed and the service remains offline. > > > > I've bridged the error handler to one I've defined within the same > > camel context so that I could detect the salesforce exception when it > > happens and then to use the control bus to restart the route which > > then does the subscription. But seems like an overkill, especially if > > this is a bug that might end up being fixed. > > > > Has anyone else experienced this? Are there any solutions to get around > > this? > > > > Many thanks! > > > > -- > Zoran Regvart
