Those "stuck" messages, are messages that have been sent or consumed as part of an XA transaction, and the server failed (crashed?) before the XA transaction committed or rolled back. If you're familiar with XA/JTA, you'll know they're in a "prepared" state (I suggest googling on XA if you're not up to speed). So, *something* needs to decide to commit them or roll them back. That something is normally the recovery manager - this is a component of JBoss AS (see JBoss TS), not JBM, that decides this. There is a section in the use guide for how to configure XA recovery. Most probably you haven't set this up, so messages will stay "stuck" until you do. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185949#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...