Cannot start post office...
bodrin Sep 10, 2008 8:39 AMjboss-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 )