[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-198) Websphere transaction management with Hibernate

[Andrei Iltchenko (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-198?page=comments#action_23981 ] 

Andrei Iltchenko commented on HHH-198:
--------------------------------------

I am discovering this issue anew on WebSphere 6.0.2.9 and Hibernate 3.2.CR2, cf. <http://forum.hibernate.org/viewtopic.php?t=963579>.

> 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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira