Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Transaction Rolledback Exception

 
Kiran Kumar Chitturi
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Everyone,

I am getting a Transaction Rolled back exception while running my application. I am using WebSphere Application Server 5.1.1 on AIX machine.

This is the exception I got.

javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is: org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException : ; nested exception is: com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction rolled back vmcid: 0x0 minor code: 0 completed: No at com.ibm.CORBA.iiop.UtilDelegateImpl.mapSystemException(UtilDelegateImpl.java :214) at com.ibm.CORBA.iiop.UtilDelegateImpl.wrapException(UtilDelegateImpl.java:684) at javax.rmi.CORBA.Util.wrapException(Util.java:296) at app.program.ejb._IUICLCCCProcess_Stub.processLCCCRequest(_IUICLCCCProcess_Stub.java:654) at

Regards
Kiran
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I guess this is just a part of the exception stacktrace. If you look at the entire stacktrace, you might find something helpful telling you the exact cause of the exception.
 
Kiran Kumar Chitturi
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is the whole stack trace i got. "app.program.ejb._IUICLCCCProcess_Stub.processLCCCRequest(_IUICLCCCProcess_Stub.java:654) at " processLCCCRequest This is the method I am calling.

regards
Kiran
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The stacktrace does not specify the exact cause of the transaction rollback. One of the likely causes might be that your method in the bean is throwing some exception. Did you try and debug the method?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic