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
