1 2 Previous Next 16 Replies Latest reply on Jul 8, 2008 4:17 PM by Tim Fox

    Exception when starten 2nd node

    Markus Breuer Newbie

      After migration from JBossMQ to JBossMessaging i get an exception when starting the 2nd cluster node.

      2008-07-03 10:40:05,011 66685 ERROR [org.jboss.messaging.util.ExceptionUtil] (main:) SessionEndpoint[12-n9fx37if-1-oy9w37if-9w9nuy-m3g4o4c5] cre
      ateConsumerDelegate [22-t9fx37if-1-oy9w37if-9w9nuy-m3g4o4c5]
      javax.jms.InvalidDestinationException: No such destination: JBossQueue[intern.reporting.event] has it been deployed?
       at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegateInternal(ServerSessionEndpoint.java:1838)
       at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionEndpoint.java:252)
       at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createConsumerDelegate$aop(
      SessionAdvised.java:94)
       at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsu
      merDelegate_8721389917985689973.java)
      



      2008-07-03 10:47:18,428 500102 ERROR [com.materna.buc.macs.comp.dm.svc.email.EMailReceiver] (Thread-55:) DeliveryService.EMAIL.test.email.0,serg
      el] -103011 com.materna.buc.macs.exception.MacsJmsException: javax.jms.JMSException: There is no administratively defined queue with name:Deliv
      eryService.EMAIL.test.email.0 -103011
      com.materna.buc.macs.exception.MacsJmsException: javax.jms.JMSException: There is no administratively defined queue with name:DeliveryService.EM
      AIL.test.email.0 -103011
       at com.materna.buc.macs.basics.jms.MacsJmsObjects.setQueueSession(MacsJmsObjects.java:104)
       at com.materna.buc.macs.basics.jms.MacsJmsClient.getQueueObjectsEx(MacsJmsClient.java:351)
       at com.materna.buc.macs.basics.jms.MacsJmsClient.getQueueObjects(MacsJmsClient.java:413)
       at com.materna.buc.macs.comp.dm.svc.BaseJmsReceiver.reconnectToJMS(BaseJmsReceiver.java:103)
       at com.materna.buc.macs.comp.dm.svc.BaseJmsReceiver.receiveNextMsg(BaseJmsReceiver.java:187)
       at com.materna.buc.macs.comp.dm.svc.email.EMailReceiver.run(EMailReceiver.java:240)
       at java.lang.Thread.run(Thread.java:595)
      


      It looks like a problem with the queues. The queues are deployed to deploy-hasingleton and work an the first (master) node. The 2nd node seems not to find these queue, even they are deployed to its deploy-hasingleton.

      What wrong?

        • 1. Re: Exception when starten 2nd node
          Markus Breuer Newbie

          I tried it in the other way and moved the queue definitions from deploy-hasingleton to deploy folder.

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


          Both servers are now starting without any error, the queues are found.
          My test-app does following:

          1. call session bean
          2. session bean puts message to queue A
          3. mdb (queue A) receives the message

          Locally this works fine. Then i moved 3. to the other node and started again. 1.+2. work but 3. (now on other cluster node) does not receive the message.

          What's wrong?




          • 2. Re: Exception when starten 2nd node
            Andy Taylor Master

            MDB's will only consume messages locally. You should have the same MDB's on all nodes.

            • 3. Re: Exception when starten 2nd node
              Markus Breuer Newbie

              I am doing a smoke test. The queue is filled and the local node crashes. I expect another node to process these messages. What happens, if the local node is not recoverable (e.g. hardware defect)?


              • 4. Re: Exception when starten 2nd node
                Andy Taylor Master

                 

                I expect another node to process these messages. What happens, if the local node is not recoverable (e.g. hardware defect)?


                If one node goes down then another node will take over its current state and start delivering to its own local MDB. All this can be found in the User documentation found at http://www.jboss.org/jbossmessaging/docs/index.html

                • 5. Re: Exception when starten 2nd node
                  Markus Breuer Newbie

                  I read this document but it gives me no answer. The only section which references MDB is the example section. But this does not explain how an failover works with an MDB.
                  From reading this forum I learned that jboss messaging prefers the local node as well.

                  Let me go back to my ealier example (s.a.)

                  You said MDB consume locally. Correct me: i deployed 2 local queue, each on any node. I put message to the queue an node A. If node A crashed the messages hang in this (local) queue. Right?

                  Perhaps my approach is wrong. Goal is following scenario:

                  - any node may produce messages
                  - any node may consume messages
                  - if a node crashes, the other must do the work. Messages should not be left unprocessed in a (local) queue

                  Question:
                  1. Should the queues be deployed local the any node?
                  2. Should the queues be deployed as ha-singleton?


                  • 6. Re: Exception when starten 2nd node
                    Andy Taylor Master

                     

                    But this does not explain how an failover works with an MDB


                    MDB's are outside the scope of JBM. You can find more information from the app server guys or the app server docs.

                    You should have
                    if a node crashes, the other must do the work. Messages should not be left unprocessed in a (local) queue


                    Messages will never be left unprocessed, The MDB on node A will consume messages from the queue on node A, and the MDB on node B from the queue on node B. If node A goes down, its state is replicated on node B so the messages will then be consumed on node B.


                    • 7. Re: Exception when starten 2nd node
                      Markus Breuer Newbie

                       

                      "ataylor" wrote:
                      But this does not explain how an failover works with an MDB


                      MDB's are outside the scope of JBM. You can find more information from the app server guys or the app server docs.


                      ;-)

                      The app server 4.2.2 docs don't describe how jms works with new messaging. Even there's a note, that future revision will use new jboss messaging. Also it notes that messaging will work completely different from jbossmq.
                      The newer 5.0.0 jbossas doc is not accessible for me.
                      ( (http://labs.jboss.com/file-access/default/members/jbossas/freezone/docs/Clustering_Guide/beta500/html-single/index.html)



                      You should have
                      if a node crashes, the other must do the work. Messages should not be left unprocessed in a (local) queue


                      Messages will never be left unprocessed, The MDB on node A will consume messages from the queue on node A, and the MDB on node B from the queue on node B. If node A goes down, its state is replicated on node B so the messages will then be consumed on node B.


                      :o)

                      My example even does not work. But as I understand, you are (as messaging-developer) out of scope for this problem. Which forum I should post to?
                      Is there another way to get the latest jbossas (beta) docs?

                      And last but not least what is your opinion of using jboss messaging together with jbossas 4.2.2 in a clustered environment?






                      • 8. Re: Exception when starten 2nd node
                        Andy Taylor Master

                        You should find all you need at http://www.jboss.org/jbossas/

                        And last but not least what is your opinion of using jboss messaging together with jbossas 4.2.2 in a clustered environment?


                        If you want clustered queues or topics and transparent failover this is the way to go.

                        • 9. Re: Exception when starten 2nd node
                          Tim Fox Master

                           

                          "mbreuer" wrote:

                          The app server 4.2.2 docs don't describe how jms works with new messaging. Even there's a note, that future revision will use new jboss messaging. Also it notes that messaging will work completely different from jbossmq.


                          What do you expect ?

                          JBoss AS 4.2.2 contains JBoss MQ *not* JBoss Messaging, so it's obviously not going to contain JBM documentation !!

                          The first version of JBoss AS to contain JBM is AS 4.3.

                          JBoss Messaging can be installed into JBoss AS 4.2.2 but that means removing JBoss MQ as per the instructions in the user guide.

                          Have you read the user guide?

                          Hint: Go to jboss.org and follow the links.


                          • 10. Re: Exception when starten 2nd node
                            Markus Breuer Newbie

                             

                            "timfox" wrote:
                            "mbreuer" wrote:

                            The app server 4.2.2 docs don't describe how jms works with new messaging. Even there's a note, that future revision will use new jboss messaging. Also it notes that messaging will work completely different from jbossmq.


                            What do you expect ?


                            I expect a manual describing how new jboss messaging(jms) works with as.
                            You are right, jbossas 4.2.2 comes with jbossmq, so it does not reference jboss messaging. But newer manuals (5.0.0 beta) have no changes to the clustering section, it also adresses jbossmq.

                            As ataylor described, the jboss messaging developers are not responsible for the integration into jbossas. So I will start a post to that forum.



                            Have you read the user guide?

                            Hint: Go to jboss.org and follow the links.


                            JBoss Messaging Users Guide? Yes, i read it but is does not fill the gap between messaging and as.

                            JBossAS Users guide? Yes, but it adresses JBossMQ. (4.2.2) The "Clustering Guide" link to as 5.0.0 is not acessible, the configuration guide link is accepted, but the "newer" doc is unchanged in the clustering section. :(






                            • 11. Re: Exception when starten 2nd node
                              Tim Fox Master

                               

                              "mbreuer" wrote:

                              You are right, jbossas 4.2.2 comes with jbossmq, so it does not reference jboss messaging. But newer manuals (5.0.0 beta) have no changes to the clustering section, it also adresses jbossmq.


                              JBoss 5 is still a beta.

                              If you used EAP 4.3 you would find the documentation already refers to JBoss Messaging.

                              Since you are using 4.2 I assume you are not a paying support customer and are relying on free support in this forum.

                              If you would like to volunteer to "fill the gap" and bring the JBoss AS 5 documentation up to date, I shall create a JIRA task and assign it you?

                              What's your JIRA user name?

                              Thanks for offering to help out :)

                              • 12. Re: Exception when starten 2nd node
                                Markus Breuer Newbie

                                 

                                "timfox" wrote:
                                "mbreuer" wrote:

                                You are right, jbossas 4.2.2 comes with jbossmq, so it does not reference jboss messaging. But newer manuals (5.0.0 beta) have no changes to the clustering section, it also adresses jbossmq.


                                JBoss 5 is still a beta.

                                If you used EAP 4.3 you would find the documentation already refers to JBoss Messaging.

                                Since you are using 4.2 I assume you are not a paying support customer and are relying on free support in this forum.

                                If you would like to volunteer to "fill the gap" and bring the JBoss AS 5 documentation up to date, I shall create a JIRA task and assign it you?

                                What's your JIRA user name?

                                Thanks for offering to help out :)


                                :o)

                                You are confusing me! A doc already is existing for 4.3 (just say paying customers). For 4.2 (say non-paying customers) the doc is missing.
                                In general i could write a doc filling this gap. But this is a hen-egg-problem. How can I get the required information for docs?

                                Please solve my confusion ...




                                • 13. Re: Exception when starten 2nd node
                                  Markus Breuer Newbie

                                  Hi Tim, I am still waiting for your response!

                                  Are you just kidding? Or was it a serious question?

                                  • 14. Re: Exception when starten 2nd node
                                    Tim Fox Master

                                    I still don't really understand what doc you are looking for.

                                    The user guide explains clustered connection factories, load balancing policies etc. I'm sure it could be improved but I don't think the information is missing.

                                    1 2 Previous Next