• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

CORBA.TRANSACTION_ROLLEDBACK in Websphere

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
The scenerio here is
JSP - Session Bean - Entity Bean - Oracle database
Application Server - Websphere
I am getting CORBA.TRANSACTION_ROLLEDBACK exception when the CMP entity bean is interacting with database.
This exception is being thrown whenever there is an error in database side while inserting or updating the data through Entity Beans.
My question is how to trap the specific database error in EJB client wherein I am always getting TRANSACTION_ROLLEDBACK exception which doesn't specify the exact error.
Thanks in advance for reply.
Kamal
 
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My suggestion would be in your server-side code, catch SQLException and throw an application exception with the original exception details and probably theh SQL statement as well. That will at least give you a clue where to start and what might go wrong.
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
TRANSACTION_ROLLBACK is the most general WebSphere EJB exception. The other exception is actually wrapped within it. You can look in the stdout log file and it will include all of the SQL exception information you need.
Kyle Brown
------------------
Kyle Brown,
Editor of Enterprise Java (tm) Programming with IBM Websphere
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic