[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5690?page=c...
]
Nikita Koksharov commented on HHH-5690:
---------------------------------------
I think, the problem is not in specific the cache-provider. This issue repeats on any
transaction-strategy cache - JBossCache, Infinispan.
You can run attached tests which uses org.hibernate.cache.HashtableCache (default
hibernate cache) and the bug will be the same.
So if problem the same for all transactional cache-provider, i think maybe
transaction-strategy should be fixed.
Inserted data remains in 2L Cache after rollback
------------------------------------------------
Key: HHH-5690
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5690
Project: Hibernate Core
Issue Type: Bug
Components: caching (L2)
Affects Versions: 3.5.6, 3.6.0
Reporter: Nikita Koksharov
Attachments: TransactionalCacheableItem.java, TransactionalInsertedDataTest.java
For entities with Transactional caching strategy, inserted data remains in 2L cache after
transaction rollback.
Testcase attached.
testcase used from this bug
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5490
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira