[ 
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737424#comment-16737424
 ] 

Huy Nguyen commented on CAMEL-10849:
------------------------------------

[~zregvart] [~lb] In version 2.23.0 when I set initialReplayIdMap to a value 
when the route starts everything behave like normal and I am fine with the 
replays. I'm getting an issue every time the route re-subscribes it tries to 
replay from the map again. The initialReplayIdMap needs to zero out (don't see 
any code that modifies the initialReplayIdMap) so we can default to -1 so we 
can wait for new replay ids. Eventually if i leave the route on for over 24 
hours it eventually breaks because the replay id 24h time to live.

 

My app keeps track of the last replay id that happens so if the app is down at 
startup it will replay from the last replay id and listens for new ones.

 

Thanks for any help. 

> Salesforce: subscription channel created per component
> ------------------------------------------------------
>
>                 Key: CAMEL-10849
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10849
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-salesforce
>            Reporter: Luca Burgazzoli
>            Assignee: Zoran Regvart
>            Priority: Major
>             Fix For: 2.19.0
>
>
> If I creates two salesforce consumers, I can't set different options per 
> channel as the client is configured on component level so i.e. you can't set 
> a per channel replay id as only the first one is taken into account:
> {code:java}
>     from('salesforce:comments-1?updateTopic=true&sObjectQuery=SELECT Id, 
> CommentId__c FROM Comment_Event__c')
>         
> .to("log:salesforce-comments?level=INFO&showHeaders=false&multiline=false")
>     from('salesforce:comments-2?updateTopic=true&sObjectQuery=SELECT Id FROM 
> Case')
>         
> .to("log:salesforce-cases?level=INFO&showHeaders=false&multiline=false")
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to