I've inheritted an application that I am attempting to get to run under JBoss 4.0.5GA and JBoss Messaging 1.2 SP1. When the application is deployed, I get the exception posted below and the MDBs don't work.
I know that DestinationManager is no longer used. When I look in the 4.0.5 source for JMSContainerInvoker I found that it has the use of DestinationManager service hard coded.
Did I miss a configuration step or is this a defect? Is there a work-around if the latter?
Thanks,
Rick
2007-04-14 09:21:46,656 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected for InfoStreamerMDB
org.jboss.deployment.DeploymentException: Error during topic setup; - nested throwable: (javax.management.InstanceNotFoundException: jboss.mq:service=DestinationManager is not registered.)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:720)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428)
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:523)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:653)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.createDestination(JMSContainerInvoker.java:1113)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:659)
... 2 more
I found the source of this problem - jboss.xml was botched with the message-driven sections defined in the wrong scope.