Details
-
Bug
-
Resolution: Done
-
Major
-
fuse-7.10-GA
-
None
-
False
-
None
-
False
-
%
-
Todo
-
Description
Under high load, org.apache.camel.component.jms.reply.MessageSelectorCreator.get() generates a wrong ID, "JMSCorrelationID='".
You can observe it through the TRACE level logging:
2022-04-02 11:17:02,045 TRACE Camel (xxx_1.0.0) thread #644 - QueueReplyManager[xxx] Using MessageSelector[JMSCorrelationID=']
Since "JMSCorrelationID='" is invalid, camel-jms close the existing listener and refresh another JMS Connection which leads to the performance issue.
Attachments
Issue Links
- links to