[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3472) JTASessionContext broken for WebSphere

[123 (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31173#action_31173 ] 

123 commented on HHH-3472:
--------------------------


Hi Steve,

      I ran fine using Hibernate 3.1 but when I switched to 3.3.1, I got an looping error at the method call JTATransactionFactory.getUserTransaction. The WAS version is 6.1.0.17.

Thx,
Jack


	at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
	at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
	at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
	at org.hibernate.transaction.JTATransactionFactory.createTransaction(JTATransactionFactory.java:149)
	at org.hibernate.jdbc.JDBCContext.registerSynchronizationIfPossible(JDBCContext.java:195)
	at org.hibernate.jdbc.JDBCContext.<init>(JDBCContext.java:99)
	at org.hibernate.impl.SessionImpl.<init>(SessionImpl.java:240)
	at org.hibernate.impl.SessionFactoryImpl.openSession(SessionFactoryImpl.java:557)
	at org.hibernate.context.JTASessionContext.buildOrObtainSession(JTASessionContext.java:152)
	at org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:111)
	at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:574)
	...
	... 77 more

> JTASessionContext broken for WebSphere
> --------------------------------------
>
>                 Key: HHH-3472
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3472
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.3.0.CR2
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 3.3.1, 3.4
>
>         Attachments: HHH-3472.patch
>
>
> Basically the notion of "transaction identifier" should have been used in all references to the currentSessionMap, but it was not.
> On a side-note, this is yet another perfect illustration of why some user who actually uses Hibernate on WebSphere should be maintaining all this WebSphere-related code...

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