ok I'll try 3.6 and 3.7 snapshot and I'll let you know. If the issue is still there, I'll create a ticket and will include all the steps I took to replicate the issue.
Many thanks for looking into this. Cheers andy On Sat, Nov 28, 2020 at 7:36 PM Claus Ibsen <[email protected]> wrote: > > Hi > > There are some fixes to the camel-salesforce component coming in 3.7. > But they are afair not so related to connectivity. > > But according to your description then restarting the route fixes it. > Can you create a JIRA ticket. And if possible try with 3.6.0 or > 3.7.0-SNAPSHOT if you can reproduce it there. It helps when its tested > with as new code as possible. > > On Sat, Nov 28, 2020 at 8:40 AM Andy Stebbing <[email protected]> > wrote: > > > > I'm using 3.5. > > > > thanks > > > > On Fri, Nov 27, 2020 at 4:16 PM Claus Ibsen <[email protected]> wrote: > > > > > > Hi > > > > > > What version of Camel are you using? > > > > > > 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! > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > http://davsclaus.com @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
