This looks like a bug.
I should have this fixed within the next couple of
days for 3.0.7
I'm encountering the same problem as described, and I have a few questions.
1. When is 3.0.7 going to be released?
2. Can you please specify more about this problem (after how many messages does it occur, with what expiration time, etc.)?
3. If I use the workaround suggested i.e. set the expiration time to 0, should I clean the queue once in a while, or is it enough? (I don't really care if some messages hang in the queue, as long as the MDB doesn't stop consuming the messages at all)?