]
Rafael de Albuquerque Ribeiro commented on HHH-5019:
----------------------------------------------------
Hi all,
I've just finished an implementation that seems to work using UOW. It is available at
. I am not comfortable with the getLocalId method since I changed it so it does not depend
on the old API and I am not sure whether the doNonTransactedWork is working but the
doIsolatedWork for transacted work is working and tested.
Best regards,
Rafael Ribeiro
@TableGenerator throws Unsupported exception - error performing
isolated work
-----------------------------------------------------------------------------
Key: HHH-5019
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.4.sp1, 3.2.5, 3.2.6, 3.2.7,
3.3.0.CR1, 3.3.0.CR2, 3.3.0.GA, 3.3.0.SP1, 3.3.1
Environment: Hibernate Core 3.3.1, MySQL, Websphere 6.1 with EJB3.0 Feature pack
Reporter: Tulips
While implementing GenerationType.TABLE strategy with Hibernate as the persistence
provider, id generation throws
javax.persistence.PersistenceException: org.hibernate.HibernateException: error
performing isolated work
[3/18/10 14:40:41:533 IST] 0000002d SystemErr R at
org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614)
--------------------------------------------------------------
3/18/10 14:40:41:533 IST] 0000002d SystemErr R Caused by:
org.hibernate.HibernateException: error performing isolated work
at
org.hibernate.engine.transaction.Isolater$JtaDelegate.delegateWork(Isolater.java:166)
at org.hibernate.engine.transaction.Isolater.doIsolatedWork(Isolater.java:64)
at
org.hibernate.engine.TransactionHelper.doWorkInNewTransaction(TransactionHelper.java:74)
at
org.hibernate.id.MultipleHiLoPerTableGenerator.generate(MultipleHiLoPerTableGenerator.java:210)
Looking at the
Isolater.doIsolatedWork( work, session );, implementation
try {
// First we need to suspend any current JTA transaction and obtain
// a JDBC connection
surroundingTransaction = transactionManager.suspend();
if ( log.isDebugEnabled() ) {
log.debug( "surrounding JTA transaction suspended [" + surroundingTransaction
+ "]" );
}
This happnes only with WebsphereExtendedTransactionManagerLookup as the
hibernate.transaction.manager_lookup_class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: