Clustered MDBs cannot be initialized during server startup

[vegecat]

Hi, all

I have developed a MDB (EJB 3.0) to process messages. I hot-deployed the bean (and the associated .xml file) to the farm directory of a clustered node. There was no error message and my bean worked. However, if I shut down the server and restarted it, the MDB would not be successfully deployed during the server startup process. the error message is like this:

14:31:36,760 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:service=EJB3,name=org.jboss.tutorial.clustering.bean.Dura
bleTopicBean
State: FAILED
Reason: javax.naming.NameNotFoundException: DefaultJMSProvider not bound

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:service=EJB3,name=org.jboss.tutorial.clustering.bean.Dura
bleTopicBean
State: FAILED
Reason: javax.naming.NameNotFoundException: DefaultJMSProvider not bound

Here is my .xml file that was also deployed to the farm directory together with the MDB:

<?xml version="1.0" encoding="UTF-8"?>


topic/tutorial/example
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



Any comments are appreciated.

[vegecat]

sorry about duplicate posts. It sucks that I cannot delete my own posts.