Obtaining the original JDBC exception from an EJBException?

Question

Hello All,
I am using EJB3 on Glassfish using the default TopLink persistence manager. Within a Session Bean, when the persistence manager catches a DB exception, it marks the transaction to be rolled back, and throws an EJBException, in turn wrapping a RollbackException. Now I was expecting to be able to get the original jdbc exception out of the caused by exception of one of these exceptions, but it is not.
It is important that I do retrieve the original exception, as I need to report back to the users what the problem is, and to do this I need to analyse the SQL error codes.
Note that these are the DB exceptions caught by toplink during managed transactions (e.g. an EJB persist or merge), not exceptions thrown by our code.
Does anyone know if it is possible to get this information from Toplink?
Edited by: user11973327 on Oct 4, 2009 7:19 AM

Answer 1

It is odd that Glassfish would throw an exception on marking the transaction for rollback, and ignore the thrown error. You might wish to check with Glassfish on this. What version of TopLink are you using? A similar issue on WLS was fixed in EclipseLink, you may wish to try the latest EclipseLink release.
You could also call flush() in your SessionBean to obtain the real database exception.
James : http://www.eclipselink.org : http://en.wikibooks.org/wiki/Java_Persistence