Hi,

I am using Hibernate 2.1.2 deployed under WebSphere 5.1 on an iSeries (AS/400) machine. The following warnings are being issues every time I close the session -

[16/04/04 12:18:21:936 BST] 9081a556 JDBCException W net.sf.hibernate.util.JDBCExceptionReporter SQL Warning: 0, SQLState: 01H30
[16/04/04 12:18:22:007 BST] 9081a556 JDBCException W net.sf.hibernate.util.JDBCExceptionReporter The active transaction was committed.

Looking at previous posts, this appears as thoguh it could be related to the fact that webSphere automatically returns the connection to the pool after the transaction is committed, and hibernate tryies to get SQL Warnings after this. This was posted in JIRA as HB337, but look slike it was fixed a while ago.

I am guessing that this message is hibernate reporting that it has trapped this condition - is this the case? Has anyone found a way of stopping WebSphere from doing this?

Cheers,

Colin

Just wondering if this problem was ever resolved. I'm getting the same log messages. -- Peter

Hey, i get the same messages, using hibernate 2.1.7c on websphere.

[1/16/06 13:58:10:502 CET] 2d3a8d7c JDBCException W net.sf.hibernate.util.JDBCExceptionReporter SQL Warning: 0, SQLState: 01H30
[1/16/06 13:58:10:560 CET] 2d3a8d7c JDBCException W net.sf.hibernate.util.JDBCExceptionReporter The active transaction was committed.

Anyone found out the reason for this?

Thanks

to suppress message
JDBCException W net.sf.hibernate.util.JDBCExceptionReporter logWarnings
SQL Warning: 0, SQLState: 01H30


In server.xml:

net.sf.hibernate.util.JDBCExceptionReporter=severe

<services xmi:type="traceservice:TraceService" xmi:id="TraceService_1173184185401" enable="true" startupTraceSpecification="*=info:net.sf.hibernate.util.JDBCExceptionReporter=severe" traceOutputType="SPECIFIED_FILE" traceFormat="BASIC">
<traceLog xmi:id="TraceLog_1173184185401" fileName="${SERVER_LOG_ROOT}/trace.log" rolloverSize="20" maxNumberOfBackupFiles="1"/>


Herman Vierendeels