The BasicQueue.removeAllMessages is not handling removal of msgs that have events (timeouts for example) when they are also unacknowledged. The usage that produced this issue looks to be an invalid attempt to unsubscribe a durable subscription with active msgs, but the handling of the error is leaving the subscription in a broken state. Its seems that both the BasicQueue.removeAllMessages attempt to drop msgs that have already been dropped as well as the AbstractStateManager.setDurableSubscription handling of the unsubscribe need to be cleaned up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028190#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...