Hibernate prints some duplicated information into the log when a save operation fails (for example due to a trigger failure).

Here[1] it can be seen that the error is logged when catching the exception, but also the sqlExceptionHelper process the exception stack, printing the error messages. Due to this, duplicated information may appear in the log.

See an example, with Oracle as the underlying database:

_104788 [http-bio-8080-exec-5] ERROR org.hibernate.engine.jdbc.batch.internal.BatchingBatch - HHH000315: Exception executing batch [java.sql.BatchUpdateException: ORA-20000: @20532@
ORA-06512: at “TAD_HB.AD_WINDOW_MOD_TRG”, line 78
ORA-04088: error during execution of trigger ‘TAD_HB.AD_WINDOW_MOD_TRG’
], SQL: update AD_Window set Updated=?, UpdatedBy=?, Name=? where AD_Window_ID=?
104806 [http-bio-8080-exec-5] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ORA-20000: @20532@
ORA-06512: at “TAD_HB.AD_WINDOW_MOD_TRG”, line 78
ORA-04088: error during execution of trigger ‘TAD_HB.AD_WINDOW_MOD_TRG’

104806 [http-bio-8080-exec-5] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ORA-20000: @20532@
ORA-06512: at “TAD_HB.AD_WINDOW_MOD_TRG”, line 78
ORA-04088: error during execution of trigger ‘TAD_HB.AD_WINDOW_MOD_TRG’_
...

[1 ]https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/engine/jdbc/batch/internal/BatchingBatch.java#L127