[
http://jira.jboss.com/jira/browse/JBAS-1476?page=all ]
Brian Stansberry resolved JBAS-1476.
------------------------------------
Fix Version/s: (was: JBossAS-5.0.0.Beta4)
Resolution: Out of Date
Resolving this old issue in favor of JBAS-5197. That issue reflects the approach we
decided upon on the forum.
Need to include a notion of cluster instance in the cluster view
----------------------------------------------------------------
Key: JBAS-1476
URL:
http://jira.jboss.com/jira/browse/JBAS-1476
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1
Reporter: Adrian Brock
Assigned To: Brian Stansberry
We need to include a notion of cluster instance in the cluster view id
to avoid at least the following scenario:
Client serializes a handle to a cluster which is at cluster view 22
Handle contains key DefaultPartition/HAJNDI/22
The cluster is totally restarted meaning the view reverts back to one.
The client now has a view id
DefaultPartition/HAJNDI/1
The client deserializes the handle, which will overwrite the correct cluster
view with the old invalid view.
----
This will also avoid the problem where a client talks to different clusters
with the same partition name.
----
Proposed solution:
1) At cluster formation (first node in cluster), create a cluster instance GUID
2) At cluster join (second+ node in cluster) get the GUID from the coordinator
3) Include this GUID in cluster view keys, i.e.
GUID/DefaultPartition/HAJNDI/1
--
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