[
http://jira.jboss.com/jira/browse/JBCACHE-1067?page=comments#action_12369577 ]
Javier Pedrido commented on JBCACHE-1067:
-----------------------------------------
That entity is not being modified, thats for sure. The test I'm running it is not
using JBCache directly, it is used as Hibernate second level cache.
May be it's not JBCache fault and some other JBoss component is flagging the cache
nodes as modified, but I'm very sure that my application it is not modifing the EJB3
entity of the exception.
I will try to write a small test to reproduce the bug.
Concurrent node removal detection is not working correctly in
OptimisticValidatorInterceptor.java
-------------------------------------------------------------------------------------------------
Key: JBCACHE-1067
URL:
http://jira.jboss.com/jira/browse/JBCACHE-1067
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: MonthOfBugs_200, Optimistic Locking
Affects Versions: 1.4.1.SP3
Reporter: Javier Pedrido
Assigned To: Manik Surtani
Fix For: 2.0.0.GA, 1.4.1.SP4
A fix similar to JBCache-1026 should be applied
--
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