[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2457) UnsupportedOperationException with WebSphereExtendedJTATransactionLookup

[Mark Su (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28173 ] 

Mark Su commented on HHH-2457:
------------------------------

I found this problem recently.
My env is WAS 6.1.0.11, DB2 9.1.2 and Hibernate version is 3.2.5, XA datasource configuration is done.
When program using the session.createCriteria(), UnsupportedOperationException occured.
So WAS v6.1 fixpack 9 did not fix this problem, and I don't think this is WAS's issue.
Because when I change the Hibernate version to 3.1.3, everything goes fine.


> UnsupportedOperationException with WebSphereExtendedJTATransactionLookup
> ------------------------------------------------------------------------
>
>                 Key: HHH-2457
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457
>             Project: Hibernate3
>          Issue Type: Bug
>    Affects Versions: 3.2.2
>            Reporter: Erik Post
>
> Using the WebSphereExtendedJTATransactionLookup as transaction manager lookup class results in an UnsupportedOperationException being thrown by WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter.getStatus(). This method is called by JTATransactionFactory.isTransactionInProgress().
> Would a solution be to have the TransactionManagerAdapter#getStatus method delegate to the TransactionAdapter#getStatus method?
> Also see http://forum.hibernate.org/viewtopic.php?t=966463

-- 
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