I have a singleton CMT MDB consuming on a JMS queue with a retry threshold set to 3 attempts. I made the assumption that no other messages on the queue would be consumed until the current message being processed either finishes and is consumed, or in the event of a container transaction rollback and the retry threshold is reached, the message is consumed off the source queue and pushed to the DLQ.
However, the behaviour I'm seeing is that on the retry, other messages sitting on the queue are consumed prior to the retry occurring. The singleton is working in terms of only one message at a time being processed, however the retry semantic seems odd to me in that it appears like the implementation of the retry logic is just simply pushing the message back on the queue to be consumed again in a different "thread" later on. Is this correct? If so, how do I change that behaviour so that no other messages on the queue are triggered until the message completes its processing either by consumed normally, or by being consumed and pushed to the DLQ once the retry threshold is reached? Dustin ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
