activeMQ reading order problem

[mikeplanamente <mi...@hotmail.com>]

Hi all, 

my environment: 

servicemix 4.3.1 fuse 02-05 
java 1.6.0_07 
camel 2.6 fuse 02-05 
activemq 5.4.2.fuse-04-05 

I've a strange problem: 

I have a single monothreadded camel route using camel activemq component to 
consume messages from a AMQ queue. 

case 1: 
consumer is stopped, the queue is filled with messages then the consumer is
started -> all messages are read in the right order EXCEPTED the first that
is consumed at THE END! 
In other words, the second message and the next ones are first consumed
then, once all others have been processed the first message in the queue is
consumed! 

case2: 
the consumer is started, messages are injected in the queue -> all messages
are processed in the right order, as expected. 

maybe you already had such a problem? 

in advance, many thanks to you all for your support and ideas... 

Michael. 





--
View this message in context: http://camel.465427.n5.nabble.com/activeMQ-reading-order-problem-tp5720172.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: activeMQ reading order problem

[Willem jiang <wi...@gmail.com>]

How did you stop the consumer, I'm not sure if the consumer still hold the first message when you stop the consumer.
What kind of JMS ACKNOWLEDGE did you use?

-- 
Willem Jiang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
          http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang 
Weibo: willemjiang





On Friday, September 28, 2012 at 2:43 PM, mikeplanamente wrote:

> Hi all, 
> 
> my environment: 
> 
> servicemix 4.3.1 fuse 02-05 
> java 1.6.0_07 
> camel 2.6 fuse 02-05 
> activemq 5.4.2.fuse-04-05 
> 
> I've a strange problem: 
> 
> I have a single monothreadded camel route using camel activemq component to 
> consume messages from a AMQ queue. 
> 
> case 1: 
> consumer is stopped, the queue is filled with messages then the consumer is
> started -> all messages are read in the right order EXCEPTED the first that
> is consumed at THE END! 
> In other words, the second message and the next ones are first consumed
> then, once all others have been processed the first message in the queue is
> consumed! 
> 
> case2: 
> the consumer is started, messages are injected in the queue -> all messages
> are processed in the right order, as expected. 
> 
> maybe you already had such a problem? 
> 
> in advance, many thanks to you all for your support and ideas... 
> 
> Michael. 
> 
> 
> 
> 
> 
> --
> View this message in context: http://camel.465427.n5.nabble.com/activeMQ-reading-order-problem-tp5720172.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).