[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2340?page=c...
]
Galder Zamarreno commented on HHH-2340:
---------------------------------------
Previous case link is incorrect, should be:
https://na1.salesforce.com/50030000002Y4ZP
Entity second level cache put operations should either fail silently
or provider to retry
-----------------------------------------------------------------------------------------
Key: HHH-2340
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2340
Project: Hibernate3
Type: Improvement
Components: core
Versions: 3.2.1
Reporter: Galder Zamarreno
Using JBossCache as second level cache and optimistic locking,
rollbacks can still happen in systems under load as concurrent
transactions could be modifying data in the cache.
Hibernate clients could retry the update, but it's probably better if
either, a similar silent failover mechanism was used for entity
cache, or alternatively, Hibernate to attempt a retry.
--
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