[
https://issues.apache.org/jira/browse/CAMEL-22860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053532#comment-18053532
]
Bhagyashree Ambavane edited comment on CAMEL-22860 at 1/22/26 11:30 AM:
------------------------------------------------------------------------
Kindly find reproducer below:
Please add/update below things to make code work
1) Salesforce properties and ODS URL
2) Update settings.json to point local java environment.
3) Replace platform event names
[^i360camelintegrationspubsub - Copy.zip]
*^Please run the application and trigger platform events and keep the
application active for at least one day^*
was (Author: JIRAUSER312087):
Kindly find reproducer below:
Please add/update below things to make code work
1) Salesforce properties and ODS URL
2) Update settings.json to point local java environment.
3) Replace platform event names
[^i360camelintegrationspubsub - Copy.zip]
> Camel-Salesforce - Pub/Sub API reconnect attempts causing infinite
> re-subscribe loop
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-22860
> URL: https://issues.apache.org/jira/browse/CAMEL-22860
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Affects Versions: 4.8.0, 4.8.2, 4.14.3, 4.16.0, 4.17.0
> Reporter: Bhagyashree Ambavane
> Priority: Major
> Attachments: Exception Details.txt, i360camelintegrationspubsub -
> Copy.zip
>
>
> When subscribing to multiple Salesforce Platform Events via the Pub/Sub API
> using the OAuth 2.0 JWT Bearer Flow, the Camel client enters a continuous
> re‑subscription loop. This prevents stable long‑lived event consumption.
> Authentication method: OAuth 2.0 JWT Bearer Flow.
> *Steps to Reproduce*
> Configure Camel Salesforce component with JWT bearer flow credentials.
> Subscribe to multiple Platform Events using the Pub/Sub API.
> Observe client behavior during re‑subscription attempts.
> *Observed Behavior*
> Initial subscription succeeds.
> Client attempts to re‑subscribe.
> Subscription fails due to some error.
> Instead of refreshing the JWT token, the client retries indefinitely,
> resulting in a loop of failed re‑subscriptions.
> *Impact*
> Subscriptions become unstable after re-subscription attempt.
> *Technical Notes*
> The issue appears to be related to token lifecycle management in the Camel
> Salesforce component.
> The JWT bearer flow does not support refresh tokens; instead, a new JWT
> assertion must be exchanged for a fresh access token.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
