You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We used SQLcodes from Firebird, seems that previous mapping was incomplete (HY000 is returned when no specific code is there). I have updated the mapping from FB 2.5 and now the GDScode 335544726 gets the 08006 SQLcode (so checking for the 08xxx) should work with your pool.
Submitted by: Wallace Wadge (wwadge)
Assigned to: Roman Rokytskyy (rrokytskyy)
Hi,
I'm the author of the Java connection pool BoneCP (http://jolbox.com).
According to this link:
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/core/r0sttmsg.htm
connection exceptions should trigger an SQLState code that starts with 08. For example MySQL returns broken connections as 08S01.
However one of my users reported:
15:05:08.985 [http-8080-1] WARN org.hibernate.util.JDBCExceptionReporter - SQL Error: 335544726, SQLState: HY000
15:05:08.985 [http-8080-1] ERROR org.hibernate.util.JDBCExceptionReporter - GDS Exception. 335544726. Error reading data from the connection. Reason: Error reading data from the connection.
in response to a broken connection which eventually made the pool not recognise the error condition.
The text was updated successfully, but these errors were encountered: