[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1051) Failure of one JMS Server may cause VIEW to not propogate in JBM cluster

[Clebert Suconic (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1051?page=all ]

Clebert Suconic closed JBMESSAGING-1051.
----------------------------------------

    Resolution: Done

> Failure of one JMS Server may cause VIEW to not propogate in JBM cluster
> ------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1051
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1051
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.CR1
>         Environment:  JBoss 4.2.1 EAP with JBM 1.4 HEAD running on two CentOS5  servers with a shared MySQL 5.x db.
>            Reporter: Ray Ploski
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.GA
>
>
> In a two-node JBM cluster, after one of the nodes is hard-killed (kill -9), the server cannot be restarted.  
> An "IllegalArgumentException: Cannot start post office since there is already a post office in the cluster with the same node id ([MY_SERVER_NODE]). Are you sure you have given each node a unique node id during installation?" occurs semi-frequently in a two-node JBM cluster.  
> While looking at the surviving node, you can see all members of the view (both the dead and alive) in the PostOffice.NodeIDView.
> A restart of all members of the cluster is required to resolve the issue.  
>  ERROR [org.jboss.messaging.util.ExceptionUtil] org.jboss.messaging.core.jmx.MessagingPostOfficeService at 456a5c7c startService
> java.lang.IllegalArgumentException: Cannot start post office since there is already a post office in the cluster with the same node id (172). Are you sure you have given each node a unique node id during installation?
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.start(MessagingPostOffice.java:335)
>         at org.jboss.messaging.core.jmx.MessagingPostOfficeService.startService(MessagingPostOfficeService.java:413)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
>         at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
>         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
>         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.ServiceController.start(ServiceController.java:417)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         ..

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira