[
https://issues.apache.org/jira/browse/CAMEL-17910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517917#comment-17517917
]
Claus Ibsen commented on CAMEL-17910:
-------------------------------------
In older Camel versions we use .size() > 0 which is not safe when using
concurrency - but we changed to isEmpty that is safe.
> camel-jms - InOut with reply-to-type shared - race condition
> ------------------------------------------------------------
>
> Key: CAMEL-17910
> URL: https://issues.apache.org/jira/browse/CAMEL-17910
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 3.11.6, 3.14.2, 3.16.0
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 3.11.7, 3.14.3, 3.17.0
>
>
> In org.apache.camel.component.jms.reply.MessageSelectorCreator we should use
> a local lock instance to ensure that get / timeout does not trigger
> concurrently that can render the dirty flag in wrong state, when under high
> load.
> Also add fail-safe to the JMSCorrelationID returned so it cannot return an
> empty ID in the selector JMSCorrelationID=
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
