DestinationManager is not registered

[clairecostello]

Hi All,

JBoss 4.0.2
J2SE 5.0
MS Windows Server 2003
Server config: all

I cannot deploy my MDB for the following reason:

2005-10-24 20:28:38,937 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
org.jboss.deployment.DeploymentException: Error during queue setup; - nested throwable: (javax.management.InstanceNotFoundException: jboss.mq:service=DestinationManager is not registered.)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:898)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:922)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1492)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.management.InstanceNotFoundException: jboss.mq:service=DestinationManager is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:509)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:638)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.createDestination(JMSContainerInvoker.java:1214)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:864)
... 3 more

Also, in JMX Console, jboss.mq does not have a link to the DestinationManager. I assume it's because the DestinationManager is not started, so how do I start this MBean?

TIA,
Claire.

[clairecostello]

Hi All,

Coming back to this again. Still not getting any JBossMQ queues bound in JNDI due to this destination manager problem. But here's the strange part, recently when I restarted the server, loads of test queues appeared under JNDI. And I was able to remotely connect and put messages on these queues. For example, test/TestQueue was there. Some examples are shipped with JBoss so I guess that is where they came from. When I restarted JBoss again, all the queues disappeared. So, Destination Manager went AWOL again?

Anyone any ideas on this?
-Claire

[clairecostello]

I noticed deloy\jms directory was rather bare looking. deploy-hasingleton\jms had some files in there and one contained the MBean XML for the DestinationManager. Copied all the files to deploy\jms (probably broke a cardinal rule here) and DestinationManager gets configured and I can see the MBean in JMX Console. Now I can deploy MDBs, create queues with jboss.xml and put messages on the queues.

BTW, I'm using JBoss 4.0.2.

Just thought I'd post up this extra info.
Thanks,
Claire