[
https://issues.apache.org/jira/browse/AMQ-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-2780.
-----------------------------
Resolution: Not A Problem
The priority message order in JMS is best attempt and not a guarantee that all
messages will be ordered. In some cases depending on when the message was sent
and how fast the consumer is messages can and will arrive out of priority order.
> ActiveMQ not preserving Message Order
> -------------------------------------
>
> Key: AMQ-2780
> URL: https://issues.apache.org/jira/browse/AMQ-2780
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.0
> Environment: Windows XP, JDK 1.6.0_07
> Reporter: Ryan Rolland
> Assignee: Rob Davies
> Priority: Critical
> Fix For: 5.6.0
>
> Attachments: BenchmarkSupport.java, Consumer.java, Producer.java
>
>
> I believe I have found a bug in message order delivery in ActiveMQ. I have
> taken the example benchmark consumer and producer programs and made the
> following modifications:
> 1) Added a counter to keep track manually of the message order.
> 2) Made the transmitted number of bytes per message random between 1 and
> 64 bytes.
> 3) Added a random delay between 1 and 10 seconds triggered after every
> 100000 messages transferred on the publishing side.
> After running for a few minutes I begin to see violations in the message
> delivery order. In my most recent run I have counted 54 violations over the
> course of an hour.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
