1 Reply Latest reply on Mar 7, 2007 6:07 AM by Ilya

    Problem with ejb3 mdb after going clustered

    Ilya Newbie

      Everithing worked just fine, then I decided to go clustered and made all modifications required: oracle defaultDS and correspondig xml files. Now I'm getting pretty odd exception:

      2007-03-07 00:04:57,893 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=singlecity-debug.ear,jar=singlecity-ejb-services-controller.jar,name=SMSProcessorEJB,service=EJB3 with dependencies:
      2007-03-07 00:04:57,907 INFO [EJBContainer] STARTED EJB: ru.singlecity.ejb.servicecontroller.sms.SMSProcessorBean ejbName: SMSProcessorEJB
      2007-03-07 00:04:57,941 WARN [MessagingContainer] Could not find the queue destination-jndi-name=queue/InSMSQueue
      2007-03-07 00:04:57,942 WARN [MessagingContainer] destination not found: queue/InSMSQueue reason: javax.naming.NameNotFoundException: queue/InSMSQueue
      2007-03-07 00:04:57,942 WARN [MessagingContainer] creating a new temporary destination: queue/InSMSQueue
      2007-03-07 00:04:57,945 INFO [InSMSQueue] Registration is not done -> stop
      2007-03-07 00:04:57,946 WARN [ServiceController] Problem starting service jboss.j2ee:ear=singlecity-debug.ear,jar=singlecity-ejb-services-controller.jar,name=SMSProcessorEJB,service=EJB3
      javax.management.InstanceAlreadyExistsException: jboss.mq.destination:service=Queue,name=InSMSQueue already registered.
       at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:761)
      yo see: first it thinks, that there is no such queue and then - that it already exists =(

      This queue is defined in a sar archive that is deployed in this ear.