ActiveMQMessageConsumer rollbackCounter is not accurate

[wls <su...@hotmail.com>]

I found that whenever the message being resend and receive using a new
session, it will eventually creates a new ActiveMQMessageConsumer with the
rollbackCounter  = 0. This is inaccurate whereby, i stopped the ActiveMQ
server after the message being resend for 3 times. Then i restarted it again
and re-consume the message, the rollbackCounter = 1 if a rollback is
triggered, but the RedeliveryCounter in the message properties itself is
already 4.

Currently i'm having problem also with the rollbackCounter where i use it
with the  Spring's DefaultMessageListenerContainer with the cache level =
CACHE_CONNECTION. Everytime the message being resend, the container will get
the sharedConnection and create a new session and eventually create a new
ActiveMQMessageConsumer where the rollbackCounter is forever = 1. The
message will never be sent to DLQ. 

Is this consider a bug???
-- 
View this message in context: http://www.nabble.com/ActiveMQMessageConsumer-rollbackCounter-is-not-accurate-tf3803519s2354.html#a10762312
Sent from the ActiveMQ - User mailing list archive at Nabble.com.