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

[Steve Ebersole (JIRA)]

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

Steve Ebersole commented on HHH-3472:
-------------------------------------

What happens is that you must not be setting things up correctly.  There is an underlying error that the Transaction cannot be looked up at the specified JNDI location.  at the point there is an infinite loop attempting to generate the exception.  HHH-3481

> 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