[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-198?page=co...
]
Chris Fellows commented on HHH-198:
-----------------------------------
Yea, I also was seeing something similar with H 3.2 CR4 and WS 6.
Using the comment above by Gergely Papp [17/Feb/05 03:59 AM], I added a cfg property for
jndi namespace and all works well. So the following should solve the problem:
<property name="connection.datasource">[your websphere datasource
name]</property>
<property
name="dialect">org.hibernate.dialect.OracleDialect</property>
<property
name="transaction.manager_lookup_class">org.hibernate.transaction.WebSphereExtendedJTATransactionLookup</property>
<property
name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
<property
name="jta.UserTransaction">thisNode/servers/WebSphere_Portal/jta/usertransaction</property>
Websphere transaction management with Hibernate
-----------------------------------------------
Key: HHH-198
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-198
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.0 rc 1
Environment: 1) Websphere Application developer 5.1.2 edition
2) Hibernate version: 2.1.6
3) Oracle 10g
4) Driver Oracle 10g XA thin driver (Managed Connection)
Reporter: Cem Kayan
Assignee: Gavin King
Priority: Blocker
Fix For: 3.0.1
Attachments: HibernateWAS6.0.doc
I'm trying to use Hibernate's transaction interface to lookup and use
WebsphereTransactionManager.
In my hibernate config files (at the moment i have two) ;
i configured to initializeHibernateSessionFactories (both)
there is a session facade calling a dao which are both SLSB's
I'm using CMT
SessionFacade : RequiresNew
DAO: Mandatory
during startup i have a HibernateException:
(Could not obtain WebSphere JTSXA instance)
Everthing else seems to be ok with my Wsad Server.
for more details:
http://forum.hibernate.org/viewtopic.php?t=935229&highlight=websphere
I received following message from an IBM WAS Developers ;
"The Hibernate code does not work on WebSphere Application Server 5.1.0.3 which you
are running. It is using undocumented API and it is accessing the old 5.0 classes which
are not present in 5.1 of WebSphere. It is trying to access a class JTSXA which does not
exist in 5.1 You need to go back to the open source provider for a solution on this as
this is not using the new classes in this undocumented internal api. "
In Hibernate WebSphereTransactionManagerLookup class, there are three trials but in my
case non of them is successfull.
--
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