Join notif states different for master and other members

[glassfishrobot]

(Reported in Sailfin) when an instance comes up, the master instance get JOIN notification with member's state as ALIVE. However other instances get JOIN notification with member's state as STARTING. This needs to be looked into.

Environment

Operating System: All Platform: OpenSolaris

Affected Versions

[current]

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/shoal/issues/34
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot
• Original Issue Closed By:@glassfishrobot

[glassfishrobot]

@glassfishrobot Commented Reported by sheetalv

[glassfishrobot]

@glassfishrobot Commented sheetalv said: There is an issue in Sailfin for the same : https://sailfin.dev.java.net/issues/show_bug.cgi?id=420

[glassfishrobot]

@glassfishrobot Commented sheetalv said: It is OK for instance A to see instance B's state as ALIVE while instance C sees instance B's state as STARTING or READY. All these 3 states are considered healthy for an instance for which a Join notif is sent out. A fix has gone into Shoal workspace to make sure that the most up-to-date state is returned back via LWRMulticast. A Shoal integration will make the fix available in Sailfin.

change log at : https://shoal.dev.java.net/servlets/ReadMsg?list=cvs&msgNo=535

[glassfishrobot]

@glassfishrobot Commented Was assigned to shreedhar_ganapathy

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA SHOAL-34

[glassfishrobot]

@glassfishrobot Commented Marked as fixed on Wednesday, June 23rd 2010, 4:11:06 am