-
Bug
-
Resolution: Answered
-
Low
-
3.10.3
-
None
-
Severity 2 - Major
-
1
-
Summary
After a connection reset in the logs, the application does not restablish the connection automatically leading to failing operations when attempting to create a new connection.
Environment
- SQLServer (this has been observed when running SQLServer, however other databases may be affected)
Steps to Reproduce
- N/A
Expected Results
Even after a connection reset, FishEye is able to succesfully create new connections.
Actual Results
After a connection resets in the logs:
ERROR [notificationManager1 ] com.jolbox.bonecp.ConnectionHandle ConnectionHandle-markPossiblyBroken - Database access problem. Killing off all remaining connections in the connection pool. SQL State = 08S01 ERROR [qtp965526499-17689 ] fisheye BoneCPConnectionHook-onCheckIn - Failed to clean up connection after use java.sql.SQLException: I/O Error: Connection reset
FishEye throws Cannot open connection errors when attempting to obtain a new connection from the connection pool:
WARN [notificationManager1 ] org.hibernate.util.JDBCExceptionReporter JDBCExceptionReporter-logExceptions - SQL Error: 0, SQLState: HY010 ERROR [notificationManager1 ] org.hibernate.util.JDBCExceptionReporter JDBCExceptionReporter-logExceptions - Invalid state, the Connection object is closed. ERROR [notificationManager1 ] fisheye DefaultNotificationManager-processNotifications - Error while processing notifications: org.hibernate.exception.GenericJDBCException: Cannot open connection
Workaround
A restart of FishEye will resolve this issue.