[
https://issues.apache.org/jira/browse/CAMEL-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-7658.
--------------------------------
Resolution: Cannot Reproduce
Fix Version/s: 2.15.0
Assignee: Claus Ibsen
Works today with latest code and ActiveMQ 5.11.0.
All 4 different cache levels works.
> Out of order processing of ActiveMQ queue with a single consumer with
> CACHE_NONE
> --------------------------------------------------------------------------------
>
> Key: CAMEL-7658
> URL: https://issues.apache.org/jira/browse/CAMEL-7658
> Project: Camel
> Issue Type: Bug
> Components: camel-activemq, camel-jms
> Affects Versions: 2.13.2
> Environment: Windows 7 x64. Java 7 & 8
> Reporter: Paul McCulloch
> Assignee: Claus Ibsen
> Fix For: 2.15.0
>
> Attachments: TestJMSOrdering.java
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
