[JBoss JIRA] Created: (JBCACHE-793) hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
10:02 a.m.
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
6:32 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-793) hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
[ http://jira.jboss.com/jira/browse/JBCACHE-793?page=comments#action_12344662 ]
Max Andersen commented on JBCACHE-793:
--------------------------------------
so does the optimistic locking in jbosscache "forget" the invalidation and its
version number immediatly ?
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
8:56 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-793) hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
[ http://jira.jboss.com/jira/browse/JBCACHE-793?page=comments#action_12344667 ]
Brian Stansberry commented on JBCACHE-793:
------------------------------------------
I'm not sure I understand the question, but that's never stopped me trying to
answer ;)
If JBC is managing the versions, the invalidation message carries no version; on the
recipient the node is just removed (or just its data if it has chidren).
If the caller is managing the versions, the invalidation message carries the
originator's version. This is compared to the version on the message recipient; if
the recipient version is older or the same the node is removed (or just its data if it has
children). If the recipient version is newer a CacheException is thrown, which only
propagates back to the caller if INVALIDATE_SYNC is used.
When the recipient removes the node/node-data, the version stored in the node is lost. If
there was a version in the invalidation message, that of course is lost too when the
method returns. So, I guess in that sense the recipient "forgets" the
invalidation's version number.
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
1:38 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-793) hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
[ 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
10:56 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-793) hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
[ http://jira.jboss.com/jira/browse/JBCACHE-793?page=comments#action_12344892 ]
Manik Surtani commented on JBCACHE-793:
---------------------------------------
discussing this on the all(a)hibernate.org list, I believe. Let's move the discussion
there.
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, 1.4.0.SP1
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0, 1.4.0.SP2
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
10:58 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-793) hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
[ http://jira.jboss.com/jira/browse/JBCACHE-793?page=comments#action_12344893 ]
Max Andersen commented on JBCACHE-793:
--------------------------------------
ok. so if a the id+version number from the invalidation message is not kept around then we
risk the 2nd level cache will be stale.
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, 1.4.0.SP1
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0, 1.4.0.SP2
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
3:34 a.m.
New subject: [JBoss JIRA] Closed: (JBCACHE-793) hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
[ http://jira.jboss.com/jira/browse/JBCACHE-793?page=all ]
Manik Surtani closed JBCACHE-793.
---------------------------------
Resolution: Done
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
3:34 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-793) hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
[ http://jira.jboss.com/jira/browse/JBCACHE-793?page=comments#action_12345023 ]
Manik Surtani commented on JBCACHE-793:
---------------------------------------
This JIRA task is just to fix recommended configs and wiki pages, which is now done in
JBC.
See JBCACHE-806 for fixing the way invalidations work.
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
6604
days inactive
6611
days old
7 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Manik Surtani (JIRA)
-
Max Andersen (JIRA)