[jboss-jira] [JBoss JIRA] (JBMESSAGING-1960) Node falls out of the cluster, comes back in and becomes non functioning

Yong Hao Gao (JIRA) issues at jboss.org
Thu Nov 3 06:29:00 EDT 2016


    [ https://issues.jboss.org/browse/JBMESSAGING-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13316627#comment-13316627 ] 

Yong Hao Gao commented on JBMESSAGING-1960:
-------------------------------------------

Hi,

JBoss Messaging is no longer under active development. (Now the next gen project is Artemis).
Please take a look at Artemis which offers more features and community support.



> Node falls out of the cluster, comes back in  and becomes non functioning
> -------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1960
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1960
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>            Reporter: Tushar Vaidya
>
> We are using version 5.1 GA for Jboss which has version 1.4.3 of jboss messaging.
> When a node falls out of the cluster and comes back in it is non functioning.
> Seems like node falling in and out of the cluster.
> We get following in the log:
> "CloserThread 2016-10-09 10:32:45,882 | INFO  | session=       | user=           | org.jboss.messaging.core.impl.postoffice.GroupMember | Dead members: 1 ([172.16.81.25:52847])
> CloserThread 2016-10-09 10:32:45,882 | INFO  | session=       | user=           | org.jboss.messaging.core.impl.postoffice.GroupMember | New Members : 1 ([172.16.81.25:57241])
> CloserThread 2016-10-09 10:32:45,882 | INFO  | session=       | user=           | org.jboss.messaging.core.impl.postoffice.GroupMember | All Members : 2 ([172.16.81.26:50276, 172.16.81.25:57241])"
> We also get javax.transaction.HeuristicMixedException in logs and the node in the cluster becomes non functioning. 
> Issue seems similar to 
> https://issues.jboss.org/browse/JBMESSAGING-1782
> 1. Is there a way to replicate the issue on lower test environment.
> 2. Has the issue been fixed in jboss messaging version 1.4.8 
> which jars do we need to replace?
> Current versions of messaging jars that are being used:
>  "jboss-messaging-client.jar" specVersion="5.1.0.GA"
>  "jboss-messaging-int.jar" specVersion="5.1.0.GA"
>  "jboss-messaging.jar" specVersion="1.4.3.GA" 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list