[
https://issues.apache.org/jira/browse/CAMEL-19409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789872#comment-17789872
]
Jeremy Ross commented on CAMEL-19409:
-------------------------------------
[[email protected]] [~davsclaus] [~iva123] I've spent the weekend trying to
reproduce this issue, without success.
Here's what I've tried:
* Single camel context
** Two streaming api consumer routes, only 1 set to auto-start.
** After 5 minutes, stop the running route.
** After 5 minutes, start the route that was never started.
* Single camel context
** After 5 minutes, call session.logout()
* Single camel context
** After 5 minutes, call set session token to a random string
* Multiple camel contexts, all with a single streaming api consumer route
** Context A: Auto-started route. Stop and start the route at random intervals
** Context B: Initially stopped route. Stop and start the route at random
intervals
** Context C: Auto-started route that is never stopped
Is anyone still having this issue? If we can't get a reproducer, I'd be
inclined to close this issue.
> camel-salesforce - Can not re-subscribe to CDC channel data/ChangeEvents
> ------------------------------------------------------------------------
>
> Key: CAMEL-19409
> URL: https://issues.apache.org/jira/browse/CAMEL-19409
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Affects Versions: 3.18.3, 3.19.0
> Reporter: Iva
> Priority: Major
> Fix For: 4.x
>
> Attachments: stack-with-pr.txt, stacktrace.txt
>
>
> Hello, I have problem with connection to the salesforce channel ChangeEvents.
> I am using quarkus - version 2.13.7 and camel with version 3.18.3 and when an
> error occurs my application is not re-subscribing to the channel after that.
> Do you know if it is problem from the camel version or do you have any idea
> how I can fix it? Thank you in advance
> Edit 1: You can find the stacktrace of the exception in this file
> [^stacktrace.txt]
> The problem seems to be fixed after a restart of the pod but it is not
> relevant solution. I have seen similar issue that is said to be fixed in
> version 3.14 but it looks like now I have the same problem in latest version
> https://issues.apache.org/jira/browse/CAMEL-16370
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
