activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: wrong message
Date Tue, 30 Mar 2010 17:41:16 GMT
On Tue, 2010-03-30 at 12:31 -0400, Gabe Westmaas wrote:
> Below is a slightly edited version of a tcp dump on the activemq side of a transaction
between an NMS 1.2 client and ActiveMQ 5.3.
> 
> MESSAGE
> message-id:ID:arch3.bmdc-35562-1269288301113-2:1918:-1:1:14
> 
> BEGIN
> transaction:ID:IAD2DEPLOY01-56247-634052078212143799-1:885:1
> message-id:ID:arch3.bmdc-35562-1269288301113-2:1918:0:1:14
> COMMIT
> receipt:8
> transaction:ID:IAD2DEPLOY01-56247-634052078212143799-1:885:1
> 
> ERROR
> message:Unexpected ACK received for message-id [ID:arch3.bmdc-35562-1269288301113-2:1918:0:1:14]
> 
> The observed behavior is that NMS clients cannot read any messages from the queue, but
other clients can read just fine.  If the server is restarted (with persistent messages) then
the NMS client can consume without issue.
> 
> I notice that one part of the message ID (the session ID of the producer ID - thanks
Dejan!) changes from -1 to 0 for the transaction and therefore the acknowledgement.
> 
> Does anyone have any experience with this or know where this problem might be caused?
> 
> We see it fairly regularly, but cannot reproduce it on command.
> 
> Thanks,
> Gabe
> 

Without a way to reproduce it its hard to say what the cause could be,
can you enable logging in the NMS client at the DEBUG level and submit
the logs from around the time this problem occurs?  

Regards


-- 
Tim Bish

Open Source Integration: http://fusesource.com
ActiveMQ in Action: http://www.manning.com/snyder/

Follow me on Twitter: http://twitter.com/tabish121
My Blog: http://timbish.blogspot.com/


Mime
View raw message