You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jeremy Ross (Jira)" <ji...@apache.org> on 2023/06/24 18:48:00 UTC
[jira] [Comment Edited] (CAMEL-19409) camel-salesforce - Can not re-subscribe to CDC channel data/ChangeEvents
[ https://issues.apache.org/jira/browse/CAMEL-19409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736775#comment-17736775 ]
Jeremy Ross edited comment on CAMEL-19409 at 6/24/23 6:47 PM:
--------------------------------------------------------------
[~jsightle@redhat.com] [~iva123] It's not clear to me why you'd receive a 401 in the META_SUBSCRIBE channel, but I created a PR (https://github.com/apache/camel/pull/10286) which will re-login and re-subscribe if this happens. I can't reproduce this situation, so can someone please see if this helps?
was (Author: jeremyross):
[~jsightle@redhat.com] [~iva123] It's not clear to me why you'd receive a 401 in the META_SUBSCRIBE channel, but I created a PR (|https://github.com/apache/camel/pull/10286) which will re-login and re-subscribe if this happens. I can't reproduce this situation, so can someone please see if this helps?
> 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: 3.20.7, 3.21.1, 4.0.0
>
> 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)