I face a similar problem. Sometimes, there are still messages in a queue when JBoss is shutdown intentionally for maintenance. During the next startup of JBoss, before all the EJBs are successfully deployed, the previously-queued messages have already started to be processed by the MDBs. As the processing of those queued messages requires the EJBs that are still being deployed, there are lots of NameNotFound exceptions and transaction rollbacks during JBoss startup. Can JBoss be configured to start delivering queued messages to MDBs only after the complete startup of JBoss? This capability will help a lot by removing the tons of exceptions that are not supposed to happen. By the way, I am using jboss-4.0.4.GA-Patch1. Thanks. Hann Wei View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978066#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...