[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1799) The way to detect first member in a cluster as coded in GroupMember is not correct
Howard Gao (JIRA)
jira-events at lists.jboss.org
Tue Apr 13 08:54:06 EDT 2010
[ https://jira.jboss.org/jira/browse/JBMESSAGING-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard Gao closed JBMESSAGING-1799.
-----------------------------------
Resolution: Done
> The way to detect first member in a cluster as coded in GroupMember is not correct
> ----------------------------------------------------------------------------------
>
> Key: JBMESSAGING-1799
> URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1799
> Project: JBoss Messaging
> Issue Type: Bug
> Components: JMS Clustering
> Affects Versions: 1.4.0.SP3.CP10, 1.4.5.GA, 1.4.6.GA
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 1.4.0.SP3.CP11, 1.4.6.GA.SP1
>
> Attachments: GroupMember.java
>
>
> Based on JGroups expert's advice, the way we detect if a member is the first member in the cluster is not correct.
> From Vladimir's email:
> ...JBM code assumes that if getState returns false that the first member is starting - which is not true. It just indicated that state transfer was not successful (timeout/non-serializable state/first member in cluster).
> We shall make the correct changed as Vladimir suggested (he also provided a fix, see attachment).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list