]
Steve Ebersole closed HHH-2532.
-------------------------------
Resolution: Won't Fix
This issue is fixed by HHH-2533 and the introduction of region-wide lock/release semantics
on the concurrency (access) strategy.
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
Reporter: Steve Ebersole
Assignee: Steve Ebersole
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: