This is where I wold expect INDIVIDUAL_ACK to be different from CLIENT ACK. For a given session message.acknowledge with CLIENT_ACK will ack all messages received, but the activemq INDIVIDUAL_ACK mode, just an individual message should be acknowledged.
To see if it is actually a problem, I guess a real test case is to use INDIVIDUAL ACK and ack out of order (as you are doing), but do not ack the the first message. Then verify that the first message is redelivered. With CLIENT_ACK on the same session, I would expect no redelivery, but with INDIVIDUL_ACK there should be redelivery. Some of the relevant activemq unit tests are: org.apache.activemq.JmsClientAckTest org.apache.activemq.JMSIndividualAckTest from: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/ 2009/11/11 Daroo <dariusz.szablin...@gmail.com> > > I'm wondering if this is something I should worry about. I've noticed that > the error message has changed log level between releases 5.1 and 5.3 from > SEVERE to WARNING. But still, it's not acceptable on PROD environment. > > > jwotman wrote: > > > > I'm seeing the same exception. Using the > > org.apache.activemq.ActiveMQSession.INDIVIDUAL_ACKNOWLEDGE mode because > > I'm reading the messages with one consumer and then a separate app > > acknowledges the message if all has gone well. > > I'm using 5.3. > > > > -- > View this message in context: > http://old.nabble.com/%22Could-not-correlate-acknowledgment-with-dispatched-message%22-tp26308220p26308790.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
