[
http://jira.jboss.com/jira/browse/JBCACHE-793?page=comments#action_12344669 ]
Max Andersen commented on JBCACHE-793:
--------------------------------------
ok, so it does forget that what version number is the latest one; meaning we run the risk
of getting old data into the cache if a old tx is ending on Node B after the fact that
Node A sent an invalidation out.
bummer.
hibernate-recommended-config.xml incorrectly specifies
INVALIDATION_SYNC
------------------------------------------------------------------------
Key: JBCACHE-793
URL:
http://jira.jboss.com/jira/browse/JBCACHE-793
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 1.4.0.SP1, 1.4.0
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 1.4.0.SP2, 2.0.0
Steve Ebersole has indicated that use of invalidation is inappropriate for the Hibernate
2nd level cache use case, so we shouldn't recommend it.
--
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