• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

TRANSACTION_ROLLEDBACK during create() on remote ejb

Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I have an EJB running on a WSAD 5.1 which access a remote EJB running on WAS 6.

The remote EJB uses a XA datasource.

When the create() method is called, I get the following exception:

javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:

Trace from server: 1198777258 at host li09 >>
org.omg.CORBA.TRANSACTION_ROLLEDBACK: vmcid: 0x0 minor code: 0 completed: No
at com.ibm.ws.Transaction.JTS.CoordinatorImpl.get(CoordinatorImpl.java:309)
at com.ibm.ws.Transaction.JTS.TxServerInterceptor.receive_request(TxServerInterceptor.java:119)
at com.ibm.rmi.pi.InterceptorManager.iterateReceiveRequest(InterceptorManager.java(Compiled Code))
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:599)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:463)
at com.ibm.rmi.iiop.ORB.process(ORB.java:439)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1737)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2260)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:65)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
<< END server: 1198777258 at host li09

minor code: 0 completed: No

It happens only with XA datasource.

if I deploy the same remote ejb on WAS 5, and access it from WSAD 5, it works fine.

Does anyone have a hint?
Samuel Lima
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I got the answer in another forum.

For those who are facing the same problem, go to the link below and see the solution posted by the great Andy Wilkinson.


See you.
author and cow tipper
Posts: 5000
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

You can overcome this by disabling protocol security on the WAS 6 server by
setting a custom property on the transaction service with a name of
DISABLE_PROTOCOL_SECURITY and a value of true.

Wow. You can tell the guy had been bitten by that problem a few times.

Sweet solution.

    Bookmark Topic Watch Topic
  • New Topic