]
Manik Surtani updated JBCACHE-761:
----------------------------------
Fix Version/s: 1.4.0.SP2
2.0.0
Affects Version/s: 1.4.0.SP1
1.3.0.SP3
Make connecting the channel and state transfer an atomic part of
startup
------------------------------------------------------------------------
Key: JBCACHE-761
URL:
http://jira.jboss.com/jira/browse/JBCACHE-761
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: 1.4.0.SP1, 1.3.0.SP3
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 1.4.0.SP2, 2.0.0
If an exception is thrown during initial state transfer, the channel should be
disconnected. The exception will propagate out of startService(), which in the AS will
leave the cache service in an incompletely deployed state. But the current code leaves
the channel connected, leaving a "zombie" member of the group.
Probably need to alter stopService() as well to ensure it can handle an already
disconnected channel.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: