]
Manik Surtani updated JBCACHE-772:
----------------------------------
Fix Version/s: 3.2.0.GA
(was: 3.1.0.GA)
State transfer not handled properly in case of reconnect
--------------------------------------------------------
Key: JBCACHE-772
URL:
https://jira.jboss.org/jira/browse/JBCACHE-772
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: 1.2.4, 1.2.4SP1, 1.2.4SP2, 1.3.0.GA, 1.3.0.SP1, 1.3.0.SP2,
1.3.0.SP3, 1.4.0.GA, 1.4.0.SP1
Reporter: Brian Stansberry
Assignee: Manik Surtani
Fix For: 3.2.0.GA
In createService(), TreeCache set Channel.AUTO_GET_STATE to true. This should only be
done if the cache is configured to do an initial state transfer.
That's easy to fix. What's harder to fix is what to do when region-based
marshalling is in effect. Probably, something like the following:
1) In viewAccepted, monitor for the case where a view is issue that doesn't include
the current node. Set a flag and ??? (throw exceptions when attempts are made to use the
cache???)
2) When another view is accepted that once again includes the current node, iterate
through the various marshalling regions, inactivating and then reactivating them
(reactivation will cause a partial state transfer).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: