[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2532) update/delete executeUpdate() causes problems with JBossCache (at least in opt-locking setups)
Steve Ebersole (JIRA)
noreply at atlassian.com
Tue Apr 3 13:50:04 EDT 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_26628 ]
Steve Ebersole commented on HHH-2532:
-------------------------------------
It also affects 3.2.1, 3.2.0.ga, 3.2.0.cr1, ...
This is a never-ending game dude ;)
> update/delete executeUpdate() causes problems with JBossCache (at least in opt-locking setups)
> ----------------------------------------------------------------------------------------------
>
> Key: HHH-2532
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2532
> Project: Hibernate3
> Issue Type: Bug
> Components: query-hql, query-sql
> Affects Versions: 3.1.3, 3.2.2
> Reporter: Steve Ebersole
> Assignee: Steve Ebersole
> Fix For: 3.2.3
>
>
> The underlying problem is the attempts afterwards to "clean up" the corresponding caches. Basically we attempt a clear() from within afterTransactionCompletion() which JBossCache's OptimisticNodeInterceptor complains about because we are "outside a transaction". This really needs to be redone to go through a 3-step invalidation process of the whole region, much like we do currently for indiviudual cache items.
--
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