[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1041) Bug in client side failover map updating
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1041?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1041:
--------------------------------------
One solution to this, is not to overwrite the failovermap when the update occurs, but to
*add* to the current map.
I.e the failover map on the client side after failover would read:
0-->2
1-->2
2-->0
So the client can still find the node after failure.
Bug in client side failover map updating
----------------------------------------
Key: JBMESSAGING-1041
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1041
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.CR2
Consider this scenario:
There are three nodes in the cluster: 0, 1, 2.
Failover map is as follows:
0-->1
1-->2
2-->0
There is a connection on node 1.
Node 1 is killed.
Node 2 fails over for node 1.
An update is then sent to the client with the new failover map:
0-->2
2-->0
Client side failure is then detected
The client attempts failover, but there is no failover node specified in the map any
more, since it has been updated.
Client fails to failover
--
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