JBoss-EAP-5 JMS binding on startup

Issue

At the moment we are migrating one of our major application from JBoss EAP 4.3.0.GA to JBoss EAP 5.0.1. One problem we encountered during the migration is that the JMS Binding happens after the EJB are started and we get exception such as javax.naming.NameNotFoundException: raspMessagesQueue not bound when the EJB MDB starts.

We have replaced the JMS configuration in our EAR/EJB/ directory. This is how the destination configuration looks like :

<mbean code="org.jboss.jms.server.destination.QueueService" 
 name="jboss.messaging.destination:service=Queue,name=raspMessagesQueue" xmbean-dd="xmdesc/Queue-xmbean.xml">
 <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
 <depends>jboss.messaging:service=PostOffice</depends>
 </mbean>

I can see the queue is created successfully using JBoss JMX console once the server is fully started. However it seems the server starts the EJBS before binds the JMS.

Is there any thing we need to do in order to bind the JMS before the server tries to load the EJBs?