[
https://issues.apache.org/jira/browse/CAMEL-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Byvshev updated CAMEL-22762:
-----------------------------------
Description:
If the queue is created after the application has already started, component
still keeps using null and does not refresh the queueUrl, which lead to
constant QueueDoesNotExistException error without clear explanation what is
going on.
Looks it should try to refresh it periodically or at least log queueUrl is not
detected instead of q doesn't exist.
Sourcecode investigation:
I see it just "caches" queueUrl in the constructor of PollingTask instead of
calling getQueueUrl() every poll iteration where reinitialisation logic is
placed
!image-2025-12-09-09-35-04-018.png|width=780,height=742!
was:
If the queue is created after the application has already started, component
still keeps using null and does not refresh the queueUrl, which lead to
constant QueueDoesNotExistException error without clear explanation what is
going on.
Looks it should try to refresh it periodically or at least log queueUrl is not
detected instead of q doesn't exist.
Sourcecode investigation:
I see it just "caches" queueUrl in the constructor of PollingTask instead of
calling getQueueUrl() every poll iteration where reinitialisation logic is
placed
!image-2025-12-08-17-49-23-381.png|width=550,height=524!
> aws2-sqs: queue URL stays null if the queue is created after the application
> has already started
> ------------------------------------------------------------------------------------------------
>
> Key: CAMEL-22762
> URL: https://issues.apache.org/jira/browse/CAMEL-22762
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2-sqs
> Reporter: Kirill Byvshev
> Priority: Major
> Attachments: image-2025-12-09-09-35-04-018.png
>
>
> If the queue is created after the application has already started, component
> still keeps using null and does not refresh the queueUrl, which lead to
> constant QueueDoesNotExistException error without clear explanation what is
> going on.
> Looks it should try to refresh it periodically or at least log queueUrl is
> not detected instead of q doesn't exist.
>
> Sourcecode investigation:
> I see it just "caches" queueUrl in the constructor of PollingTask instead of
> calling getQueueUrl() every poll iteration where reinitialisation logic is
> placed
>
> !image-2025-12-09-09-35-04-018.png|width=780,height=742!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
