[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3472) JTASessionContext broken for WebSphere
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3472?page=c...
]
123 commented on HHH-3472:
--------------------------
I looked into the log and it seems that the JNDI info is setup correctly.
SessionFactoryObjectFactory: JNDI lookup: hibernate/SessionFactory
SessionFactoryObjectFactory: lookup: uid=8aaafbb81c58d8f4011c58d8f8690000
Helper: Newly created SessionFactory was found in JNDI
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira