5 Replies Latest reply on Oct 13, 2008 7:05 PM by Clebert Suconic

    Cannot start post office...

    bodrin b. Newbie

      jboss-4.2.2.GA / jboss-messaging-1.4.0.SP3

      I have the following exception when restarting the JBoss / JBM :

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.messaging:service=PostOffice
       State: FAILED
       Reason: java.lang.IllegalArgumentException: Cannot start post office since there is already a post office in the cluster with the same node id (36472). Are you sure you have given each node a unique node id during installation?
       I Depend On:
       jboss.messaging:service=ServerPeer
       jboss.jca:service=DataSourceBinding,name=DefaultDS
       jboss:service=TransactionManager
       Depends On Me:
       jboss.messaging.connectionfactory:service=ConnectionFactory
       jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
       jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
       jboss.messaging.destination:service=Queue,name=TestService
       jboss.messaging.destination:service=Queue,name=TestServiceReply
       jboss.messaging.destination:service=Queue,name=payments
       jboss.messaging.destination:service=Queue,name=profiles
       jboss.messaging.destination:service=Queue,name=profiles_2
       jboss.messaging.destination:service=Queue,name=profiles_3
       jboss.messaging.destination:service=Queue,name=profiles_4
       jboss.messaging.destination:service=Queue,name=profile_subscriptions
       jboss.messaging.destination:service=Queue,name=profile_subscriptions_2
       jboss.messaging.destination:service=Queue,name=profile_subscriptions_3
       jboss.messaging.destination:service=Queue,name=profile_subscriptions_4
       jboss.messaging.destination:service=Queue,name=mapp_info_out
       jboss.messaging.destination:service=Queue,name=operation_authorization
       jboss.messaging.destination:service=Queue,name=payment_state_notification
       jboss.messaging.destination:service=Queue,name=mapp_sedo_out
       jboss.messaging.destination:service=Queue,name=sedo
       jboss.messaging.destination:service=Queue,name=client_profile_activation
       jboss.messaging.destination:service=Queue,name=wsgw_client_profile_activation
       jboss.messaging.destination:service=Queue,name=mapp_pin_reset
       jboss.messaging.destination:service=Topic,name=RFIDs
       jboss.messaging.destination:service=Topic,name=terminals
       jboss.messaging.destination:service=Topic,name=mapp_info_in
       jboss.messaging.destination:service=Queue,name=DLQ
       jboss.messaging.destination:service=Queue,name=ExpiryQueue
       jboss.messaging.destination:service=Topic,name=testTopic
       jboss.messaging.destination:service=Topic,name=securedTopic
       jboss.messaging.destination:service=Topic,name=testDurableTopic
       jboss.messaging.destination:service=Queue,name=testQueue
       jboss.messaging.destination:service=Queue,name=A
       jboss.messaging.destination:service=Queue,name=B
       jboss.messaging.destination:service=Queue,name=C
       jboss.messaging.destination:service=Queue,name=D
       jboss.messaging.destination:service=Queue,name=ex
       jboss.messaging.destination:service=Queue,name=PrivateDLQ
       jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue
       jboss.messaging.destination:service=Queue,name=QueueWithOwnDLQAndExpiryQueue
       jboss.messaging.destination:service=Topic,name=TopicWithOwnDLQAndExpiryQueue
       jboss.messaging.destination:service=Queue,name=QueueWithOwnRedeliveryDelay
       jboss.messaging.destination:service=Topic,name=TopicWithOwnRedeliveryDelay
       jboss.messaging.destination:service=Queue,name=testDistributedQueue
       jboss.messaging.destination:service=Topic,name=testDistributedTopic
      
      
      


      So I have to change the ServerPeerID on each restart
      in JBOSS_CONFIG/deploy/jboss-messaging.sar/messaging-service.xml.

      Have you any idea what could be the problem?
      (we have many JBoss nodes in the LAN running, but they should be in different partitions and each post office has uniqe ServerPeerID )

        • 1. Re: Cannot start post office...
          bodrin b. Newbie

          I'm also experiencing the problem described in
          https://jira.jboss.org/jira/browse/JBMESSAGING-1256

          Finally I have found a workaround : starting JBoss with different multicast address (-u 230.0.0.5) eleminated the above problems!

          It seems that the interaction with other nodes on the LAN is tha cause for the above two problems.

          • 2. Re: Cannot start post office...
            Clebert Suconic Master

            JBMESSAGING-1256 wasn't confirmed yet...


            I believe you just have two nodes with the same ID on the same network.

            You just need to configure your cluster properly. If you need different set of clusters on the same network, you certainly need different multicast-addresses.

            If all the nodes are part of the same cluster, they all need unique IDs.

            • 3. Re: Cannot start post office...
              bodrin b. Newbie

              No, there are no nodes with the same IDs on the LAN.

              The cluster is partitioned using different partionNames, but this seems to not help with JBM.

              http://docs.jboss.org/jbossas/jboss4guide/r4/html/cluster.chapt.html

              ...
              In order for nodes to form a cluster, they must have the exact same PartitionName and the ParitionCo
              nfig elements. Changes in either element on some but not all nodes would cause the cluster to split.
              
              ...
              


              • 4. Re: Cannot start post office...
                R B Newbie

                Has this been resolved? I am facing the same issue. I have 2 JBOSS servers setup in a cluster for JMS messaging. The Servers are given the IDs 13225 and 13226 in the deploy\jboss-messaging.sar\messaging-service.xml. When I restart one of the servers, I get the same error message:

                Reason: java.lang.IllegalArgumentException: Cannot start post office since there is already a post
                 office in the cluster with the same node id (13225). Are you sure you have given each node a unique
                 node id during installation?
                


                This happens only intermittently and not on every server restart.
                Also, another interesting thing is that the node ID in the message above is the ID of the server that is restarted. i.e. When I restart the server with ID 13225 the above message is displayed. So its as if the server is refering to its own ID.

                I do not have any other clusters setup on the same network.

                Any hints, suggestions welcome!

                Thanks.

                • 5. Re: Cannot start post office...
                  Clebert Suconic Master

                  It should be fixed on later versions of JBM. If you are using at least 1.4.0.SP3 you shouldn't be seeing this issue.