Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Cannot Reproduce
-
2.13.2
-
None
-
Windows 7 x64. Java 7 & 8
-
Unknown
Description
Messages are occasionally consumed out of order when the JMS or ActiveMQ component has a cache level name of CACHE_NONE or CACHE_SESSION.
The out of order message id is related to the previous message. For example: messages received are:
02885-DESKTOP-60405-1407148471972-3:1:2:1:315
02885-DESKTOP-60405-1407148471972-3:1:2:1:1316
02885-DESKTOP-60405-1407148471972-3:1:2:1:316
Attempts to debug cause the issue not to occur - perhaps some sort of race condition.
Test case attached. An equivalent test with plain Spring JMS, consuming via DMLC passes.