[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1027) InvalidationInterceptor should not replicate putForExternalRead()
[ http://jira.jboss.com/jira/browse/JBCACHE-1027?page=all ]
Manik Surtani closed JBCACHE-1027.
----------------------------------
Fix Version/s: 2.0.0.CR1
2.0.0.GA
1.4.1.SP4
Resolution: Done
Fixed in 2.0.0. putForExternalRead() does not exist in 1.4.x.
putFailFast...() is used in 1.4.x for pessimistic locking, but there is no equivalent with
optimistic locking. Instead the FailSilently option is used. Not keen on suppressing
invalidations based on FailSilently as it can be misleading.
So in 1.4.x, it is fixed with pessimistic locking, but not so with optimistic.
InvalidationInterceptor should not replicate putForExternalRead()
-----------------------------------------------------------------
Key: JBCACHE-1027
URL: http://jira.jboss.com/jira/browse/JBCACHE-1027
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Replication
Affects Versions: 1.4.1.SP3, 2.0.0.BETA2
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.CR1, 2.0.0.GA, 1.4.1.SP4
From looking at the code, it seems InvalidationInterceptor will send an invalidation
message for a putForExternalRead or putFailFast call. That basically means only one node
in the cluster will have a given entity cached. The interceptor should just ignore these
methods.
(Forgive me if I missed something; haven't tested this, just looked at code.)
--
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