[
https://issues.apache.org/jira/browse/CAMEL-19409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iva updated CAMEL-19409:
------------------------
Description:
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
was: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
> 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
> Reporter: Iva
> Priority: Major
> Attachments: 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)
