Given the following scenario: 1. An EJB3 Consumer Bean is tied to queue/mdbtest 2. It fails to deactivate the endpoint (unrelated problem) 3. queue/mdbtest is undeployed 4. A MDB Bean comes up which wants to attach to queue/inflowmdbtest, but that one isn't there (yet) so it goes down again 5. queue/inflowmdbtest comes up 6. Client connects to queue/inflowmdbtest and starts sending messages 7. The messages end up into the ConsumerContainer from step #1 For the moment it can be reproduced by running EJB3s consumer and jca/inflowmdb tests in sequence. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200343#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...