Last updated on AUGUST 07, 2017
Applies to:Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
***Checked for relevance on 6-Dec-2013***
Whenever OpenJPA captures an exception thrown by Oracle database (due to the triggering of a constraint in the database) it hides the error in a nested exception that it does not print in the logs. It then prints the following in the logs:
<BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBLocalHomeImpl@d2a857 threw exception: <openjpa-1.1.0-r422266:657916 fatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
The nested exception, however, is never printed in the log and there's no way of knowing what triggered it.
Customer can only see the nested exception by turning on JDBC logging.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms