Hi All,When a message is rolled back on a session, it appears that no other messages will be delivered to the consumer's listener for that session until the original message is consumed (committed). I believe that this is due to the session attempting to maintain message order, however this can quickly exhaust message processing when the number of concurrent consumers is capped.
What strategies are you using to handle this type of situation? Thanks, Geoff.
