activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "PLANAMENTE Michael EXT-OD" <michael.planamente.exter...@atos.net>
Subject activemq reading problem
Date Fri, 28 Sep 2012 07:07:27 GMT
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.


________________________________

Atos Worldline SA/NV - Chaussee de Haecht 1442 Haachtsesteenweg
- 1130 Brussels - Belgium
RPM-RPR Bruxelles-Brussel - TVA-BTW BE 0418.547.872
Bankrekening-Compte Bancaire-Bank Account 310-0269424-44
BIC BBRUBEBB - IBAN BE55 3100 2694 2444

"The information contained in this e-mail and any attachment thereto is confidential and may
contain information which is protected by intellectual property rights.
This information is intended for the exclusive use of the recipient(s) named above.
This e-mail does not constitute any binding relationship or offer toward any of the addressees.
If you are not one of the addressees , one of their employees or a proxy holder entitled to
hand over this message to the addressee(s), any use of the information contained herein (e.g.
reproduction, divulgation, communication or distribution,...) is prohibited.
If you have received this message in error, please notify the sender and destroy it immediately
after.
The integrity and security of this message cannot be guaranteed and it may be subject to data
corruption, interception and unauthorized amendment, for which we accept no liability."

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message