Hi Sowjanya, there's a discussion on CAMEL-12484[1] that might help in this case also, adding idleTimeout=5000 to httpClientProperties. And you're very welcome to create a JIRA issue and/or work on a contribution via pull request for this specific issue/suggestion,
thanks, zoran [1] https://issues.apache.org/jira/browse/CAMEL-12484 On Wed, Oct 3, 2018 at 10:17 PM Sowjanya Mudimala <sowjanya.mudim...@gmail.com> wrote: > > version: 2.23.0 > > I have a stand alone java app that uses camel to subscribe to > salesforce platform event. > I see frequent disconnects from salesforce causing the subscription > client to fail at some point. > attached the debug logs (1.txt). > > I am hitting the same issue with both AuthenticationType.USERNAME_PASSWORD and > AuthenticationType.JWT. > > doesn't seem like the camel-salesforce component retries on below > message ( when advice is reconnect=none). > > [CHANNEL:META_CONNECT]: {clientId=4ax18g474mdxneef13qtpln3p55cw, > advice=(reconnect=none{reconnect=none, interval=0}, > channel=/meta/connect, id=15, error=403::Unknown client, > successful=false} > > Found https://developer.salesforce.com/forums/?id=906F0000000ApCYIA0. > > Can we follow the suggestion " whenever 403 error occurs you will be > getting connection broken. SO do one thing add listener > metaUnSucessfulListener. > Once you recieve the error, the method will get called and in this > method first unsubsicribe the existing insance of cometd, create fresh > instance." > Note that I am hitting this issue even after disabling salesforce > lightening mobile alerts. > > few other relevant links: > https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/streaming_handling_errors.htm > > Thanks, > Sowjanya. -- Zoran Regvart
