[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-2340) Entity second level cache put operations should either fail silently or provider to retry
Max Rydahl Andersen (JIRA)
noreply at atlassian.com
Mon Feb 26 13:29:32 EST 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2340?page=all ]
Max Rydahl Andersen closed HHH-2340:
------------------------------------
Resolution: Rejected
It is up to the clients to decide how important it's for them to retry. Transparent retry is not a task for hibernate.
The underlying issue in jbcache causing the issue is found at http://jira.jboss.com/jira/browse/JBCACHE-956 and http://jira.jboss.com/jira/browse/JBCACHE-961
> 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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list