[Hibernate-JIRA] Created: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work
4:15 a.m.
@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.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6,
3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2, 3.2.1
Environment: Hibernate Core 3.3.1, MySQL, Websphere 6.1 with EJB3.0 Feature pack
Reporter: Rohini
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:30 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019?page=c...
]
Tulips commented on HHH-5019:
-----------------------------
Websphere suggested fix to resolve this issue for its default JPA provider -
http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21287383, does not seem to apply
for Hibernate.
persistence.xml is provided with both JTA and Non-JTA datasource specified.
<persistence-unit name="test1">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>jdbc/transDS</jta-data-source>
<non-jta-data-source>jdbc/nonTransDS</non-jta-data-source>
<class>com.test.TestEntity</class>
<exclude-unlisted-classes>false</exclude-unlisted-classes>
<properties>
<property name="hibernate.dialect"
value="org.hibernate.dialect.MySQLDialect" />
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.CMTTransactionFactory"/>
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.WebSphereExtendedJTATransactionLookup"/>
<property name="hibernate.transaction.flush_before_completion"
value="true"/>
<property name="hibernate.transaction.auto_close_session"
value="true"/>
<property name="hibernate.current_session_context_class"
value="jta"/>
</properties>
</persistence-unit>
I beleive this could be because - doIsolatedWork(work, session) method of
org.hibernate.engine.transaction.Isolater makes a JTADelegate for all CMT transactions,
which results in Unsupported exception in case Websphere appserver.
@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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:11 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019?page=c...
]
Petr H commented on HHH-5019:
-----------------------------
I think the shown stacktrace appears to be incomplete, missing the cause of that
exception.
I bet the cause is java.lang.UnsupportedOperationException thrown by
WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter suspend method.
We've been facing similar problem when doing updates of data over multiple tables.
Here Hibernate utilizes temporary tables and in many cases it might end up on attempt to
suspend current transaction (when it goes via the Isolater.etc.)
But WebSphereExtendedJTATransactionLookup doesn't implement transaction suspend/resume
and throws the UnsupportedOperationException and that's pretty bad.
I think the case described here is pretty much the same thing, though the actual data
operation is different.
Possible workarounds are something like:
use the old WebSphereTransactionManagerLookup - but this may introduce some other issues
elsewhere (and it does)
rewrite the code to avoid transaction suspension attempts
It would be really great to bring the UOWManager support into Hibernate, see:
http://itdevworld.wordpress.com/2009/01/23/websphere-uow-transactionmanag...
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2703
https://forum.hibernate.org/viewtopic.php?uid=70595&f=1&t=992310&...
and bring the transaction suspend/resume to life here as Spring does have it AFAIK.
@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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:37 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019?page=c...
]
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
http://itdevworld.wordpress.com/2010/06/27/hibernate-isolater-doisolatedw...
. 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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:37 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019?page=c...
]
Marko commented on HHH-5019:
----------------------------
The class WebSphereUOWTransactionLookup$UOWTransactionAdapter (the fix suggested by
Rafael) has an invalid implementation for the getStatus() method.
The correct implementation should be
Integer(0).equals(getLocalId()) ? Status.STATUS_ACTIVE
:Status.STATUS_NO_TRANSACTION;
@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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:37 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019?page=c...
]
Marko commented on HHH-5019:
----------------------------
Correction for previous comment:
boolean existingTx = (getUOWStatus() != UOW_STATUS_NONE &&
uowManager.getUOWType() != UOW_TYPE_LOCAL_TRANSACTION);
return existingTx ? Status.STATUS_ACTIVE: Status.STATUS_NO_TRANSACTION;
@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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:12 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019?page=c...
]
Ondrej Motlik commented on HHH-5019:
------------------------------------
It would be great to fix this issue, because we have experienced the same problems
described by Petr H and the others.
@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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4986
days inactive
5316
days old
hibernate-issues@lists.jboss.org
6 comments
6 participants
participants (6)
-
Marko (JIRA) -
Ondrej Motlik (JIRA)
-
Petr H (JIRA)
-
Rafael de Albuquerque Ribeiro (JIRA)
-
Rohini (JIRA)
-
Tulips (JIRA)