4 Replies Latest reply on Feb 14, 2009 3:44 AM by jaikiran pai

    JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly want MQ

    Michael Hönnig Newbie

      We are using JBoss Messenger 1.4.0 for a product under development. I tried to upgrade to 1.4.2 today, but all over the sudden:

      21:15:57,719 WARN [ServiceController] Problem starting service jboss.j2ee:ear=hsa.ear,jar=hsar.jar,name=QueueStatusReceiver,service=EJB3
      javax.management.InstanceNotFoundException: jboss.mq:service=DestinationManager is not registered.

      Where QueueStatusReceiver is an MDB.

      But why does it suddenly ask for a JBoss MQ service? It did work with 1.4.0 and there is nothing about MQ in our config at all and neither in our source code. Any idea where I could start checking what's going on?

      Thanks
      ... Michael

      p.s. I was pointed to this forum as a response to the same question on the JBosse Messenger forum

        • 1. Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
          jaikiran pai Master

          Please post more details including the configuration files that you use. Also please post the console logs. If the QueueStatusReceiver is configured through annotations, then post that code or else post the ejb-jar.xml and jboss.xml for that EJB.

          • 2. Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
            Michael Hönnig Newbie

            I can hardly post all my JBoss configuration. The point is: It DID WORK with JBoss Messenger 1.4.0 and I just upgraded to 1.4.2. I have not changed my other config at all.

            But anyway: Here my annotations (... is just a placeholder):

            @MessageDriven(activationConfig=
            {
            @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
            @ActivationConfigProperty(propertyName="destination", propertyValue="queue/...Status"),
            @ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="Auto-acknowledge")
            } )
            public class QueueStatusReceiver
            implements javax.jms.MessageListener

            Here the relevant part of boss-messaging.sar/destinations-service.xml:

            <mbean code="org.jboss.jms.server.destination.QueueService"
            name="jboss.messaging.destination:service=Queue,name=...Status"
            xmbean-dd="xmdesc/Queue-xmbean.xml">
            <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer
            jboss.messaging:service=PostOffice


            Which other of the vast amount of configs would you need? As I said, there is not a single word of MQ in any config file. Not a single! And yet, some JBoss part suddenly is asking for it.

            Maybe one hint: I am using sslbisocket, but I also used it with 1.4.0 and it did work (just not with PostgreSQL 8.3 anymore - but that's a different problem).

            • 3. Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
              Michael Hönnig Newbie

              Also the log of startup is HUGE. Any hints what to look for in the log?

              • 4. Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
                jaikiran pai Master

                Its a WARN message. Is it affecting your application in any way? Also are there any ERROR or exceptions? Around 10 lines before that WARN message might give some hints.