2 Replies Latest reply on Dec 23, 2006 4:54 PM by Philip Wu

    EJB3 Clustered not working, JMS MDB

    Philip Wu Newbie

      Looks like the installer for "EJB3 clustered" is broken.
      The /deploy-hasingleton/jms directory is missing.

      I tried manually copying over the necessary files to fix it, but I am still getting errors about not able to find the Custom created Queues.

      Is there something else im missing?
      Is there a way to get the installer to work properly to create the needed files?


      2006-12-23 16:03:55,624 DEBUG [org.jboss.ejb3.mdb.MessagingContainer] Got destination type Queue for ClusteredFileMoverMDB
      2006-12-23 16:03:55,624 DEBUG [org.jboss.ejb3.mdb.MessagingContainer] jndiSuffix: stitchQ
      2006-12-23 16:03:55,705 WARN [org.jboss.ejb3.mdb.MessagingContainer] Could not find the queue destination-jndi-name=queue/stitchQ
      2006-12-23 16:03:55,706 WARN [org.jboss.ejb3.mdb.MessagingContainer] destination not found: queue/stitchQ reason: javax.naming.NameNotFoundEx
      ception: queue/stitchQ
      2006-12-23 16:03:55,706 WARN [org.jboss.ejb3.mdb.MessagingContainer] creating a new temporary destination: queue/stitchQ
      2006-12-23 16:03:55,721 DEBUG [org.jboss.mq.server.jmx.DestinationManager] Attempting to create destination: jboss.mq.destination:service=Queu
      e,name=stitchQ; type=org.jboss.mq.server.jmx.Queue
      2006-12-23 16:03:55,728 DEBUG [org.jboss.ejb3.ServiceDelegateWrapper] Starting failed jboss.j2ee:ear=wubrothers.ear,jar=ejb3.jar,name=Clustere
      dFileMoverMDB,service=EJB3
      javax.management.RuntimeMBeanException
      at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:176)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)
      at org.jboss.ejb3.mdb.MessagingContainer.createTemporaryDestination(MessagingContainer.java:539)
      at org.jboss.ejb3.mdb.MessagingContainer.createDestination(MessagingContainer.java:497)
      at org.jboss.ejb3.mdb.MessagingContainer.innerCreateQueue(MessagingContainer.java:423)
      at org.jboss.ejb3.mdb.MessagingContainer.jmsCreate(MessagingContainer.java:385)
      at org.jboss.ejb3.mdb.MessagingContainer.innerStart(MessagingContainer.java:161)
      at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:147)
      at org.jboss.ejb3.mdb.MDB.start(MDB.java:126)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)



      This is how i defined my destinations-service.xml file which i placed in the deploy-hasingleton/jms directory



      <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
      org.jboss.mq.server.ReceiversImplArrayList