Hi,
Looking at this forum thread:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028373
I see an issue with the cache.remove() call being made in the
afterCompletion() block of a Synchronization. The main issue here is
that the current transaction is no longer valid by this stage (it
has, by definition, completed). From a transactional sense, what is
the purpose of remove() being called in an afterCompletion() block?
Is it intended that this remove() happens outside of the current
transaction (either in a new transaction or without one)?
Cheers,
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: [EMAIL PROTECTED]
Telephone: +44 7786 702 706
MSN: [EMAIL PROTECTED]
Yahoo/AIM/Skype: maniksurtani
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
