Databases
StackOverflow2013
Postsdbo
POCall getNextException to see the cause : How to make Hibernate / JPA show the DB server message for an exception
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCall getNextException to see the cause : How to make Hibernate / JPA show the DB server message for an exception
    primarykey
    data
    text
    <p>I am using Postgresql, Hibernate and JPA. Whenever there is an exception in the database, I get something like this which is not very helpful as it does not show what really went wrong on the DB server.</p> <pre><code>Caused by: java.sql.BatchUpdateException: Batch entry 0 update foo set ALERT_FLAG='3' was aborted. Call getNextException to see the cause. at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2621) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1837) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:407) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2754) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:268) ... 82 more </code></pre> <p>I want the exception message from the database to appear in the application's log.</p> <p>I came across <a href="http://erics-notes.blogspot.in/2008/03/java-sqlexception-chaining.html" rel="noreferrer">this article</a> which uses an Aspect to populate the exception chain which is otherwise not populated properly in case of SQLExceptions.</p> <p>Is there a way to fix this without using Aspects or any custom code. Ideal solution would involve only config file changes.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDojo
    1. USDojo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCall getNextException to see the cause : How to make Hibernate / JPA show the DB server message for an exception
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCall getNextException to see the cause : How to make Hibernate / JPA show the DB server message for an exception
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCall getNextException to see the cause : How to make Hibernate / JPA show the DB server message for an exception
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow are you outputting the exception? My experience with log4j and slf4j, I get the caused by lines for free...
      singulars
      1. POCall getNextException to see the cause : How to make Hibernate / JPA show the DB server message for an exception
      1. USmjwenk
    2. COLogging libraries do print the cause but they do so if the excption follows the exception chaining convention. i.e. each exception should return its immediate root cause through getCause() method. Apparently, SQLException does not follow this convention. The article I've linked explains the same. The author has therefore written an aspect which takes the object returned by getNextException() and sets it as the cause in the parent exception.
      singulars
      1. POCall getNextException to see the cause : How to make Hibernate / JPA show the DB server message for an exception
      1. USDojo
    3. CO@Priyank `SQLException` uses an exception chain (which can be iterated over with an iterator or using `getNextException()`) when multiple (unrelated?) exceptions occur. This concept is orthogonal to the cause-chain. In this specific example I do think it should have been set as the cause though.
      singulars
      1. POCall getNextException to see the cause : How to make Hibernate / JPA show the DB server message for an exception
      1. USMark Rotteveel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload