One other thing to note is that our redelivery behaviour differs from our competitors: http://edocs.bea.com/wls/docs81/ejb/message_beans.html The actual reason redelivery doesn't occur is that the MDB container which sits between the JMS provider and the customer provide onMessage implementation, catches the RuntimeException and wraps it in an EJBException. So when it gets to the JMS provider it's no longer a RuntimeException and the JMS provider won't redeliver the message (JMS says any RuntimeExceptions should cause redelivery). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001006#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...