Can you reproduce on the latest in the 3.2 branch?
We solved this issue with 3.2.2. We are using MS-SQL as the JMS DB.
The following steps resolved the issue:
1. Through MS SQL Enterprise Manager, list all messages in order, and delete the 1st message.
2. Restart the JMS server.
3. Restart the message consumer (receiver).
I am running 3.2.5 with postgres as the datastore for the JMS bus. And I am seeing the samething with on difference. To make the consumers to start running again all I have to do is restart the JBoss instance that the consumer is running in. This also seems to only happen under heavy load. I there a way to prevent this from happening? I cannot restart the app everytime it thinks it does not have anymore messages to process.