Open glassfishrobot opened 16 years ago
@glassfishrobot Commented Reported by sheetalv
@glassfishrobot Commented @jfialli said: Short term solution described in shoal issue 73.
Change platform to ALL since issue is not specific to MAC os.
@glassfishrobot Commented sheetalv said: short term solution in issue 73 has been added to Sailfin 0.5.
@glassfishrobot Commented sheetalv said: assigning to Joe.
@glassfishrobot Commented This issue was imported from java.net JIRA SHOAL-72
The "unable to create messenger" IOException occurs in different scenarios. One of the scenarions is when an instance is killed. before instance B can know that the instance A has been killed, it tries to send a message via ClusterManager.send() (could be to sync the DSC or for some other reason).
When such an IOException occurs, the Shoal code should check which instance is supposedly down. Then the code wait for a little while before finding the state that that instance is in. If the state is alive/aliveandready, the message should be sent again as a retry. If the instance is in in_retry_mode (i.e. it has'nt been deemed in_doubt/failed yet), then the right way of dealing with this should be decided.
Environment
Operating System: All Platform: All
Affected Versions
[current]