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
I am working with an open source application. Our team has switched to bitronix. I am seeing a weird bug, where the connection is already closed.
Exception message is [connection handle already closed]
Vendor error code [0]
SQL state code [null]
The root stack trace is -->
java.sql.SQLException: connection handle already closed
at bitronix.tm.resource.jdbc.JdbcConnectionHandle.enlistResource(JdbcConnectionHandle.java:81)
at bitronix.tm.resource.jdbc.JdbcConnectionHandle.prepareStatement(JdbcConnectionHandle.java:288)
This happens when returning to a document after doing a 'lookup' search. When returning to the document, the application will do a pessimistic lock check which queries the database for this check.
The weird thing is, this only occurs the very first time a user logs in. After getting this exception if the user tries again, it will always work. Any help is greatly appreciated!
I'll attach the complete stack trace as a file. Not sure if this is a bitronix bug or something else. I was advised to open an issue here. Any help is appreciated!
The text was updated successfully, but these errors were encountered:
Run bitronix with debug logging enabled. Find the appropriate section of the log, starting where the connection is first acquired and continuing to where the error occurs, and paste that section in a comment here (maybe a few hundred lines or so).
I am working with an open source application. Our team has switched to bitronix. I am seeing a weird bug, where the connection is already closed.
Exception message is [connection handle already closed]
java.sql.SQLException: connection handle already closed
at bitronix.tm.resource.jdbc.JdbcConnectionHandle.enlistResource(JdbcConnectionHandle.java:81)
at bitronix.tm.resource.jdbc.JdbcConnectionHandle.prepareStatement(JdbcConnectionHandle.java:288)
This happens when returning to a document after doing a 'lookup' search. When returning to the document, the application will do a pessimistic lock check which queries the database for this check.
The weird thing is, this only occurs the very first time a user logs in. After getting this exception if the user tries again, it will always work. Any help is greatly appreciated!
I'll attach the complete stack trace as a file. Not sure if this is a bitronix bug or something else. I was advised to open an issue here. Any help is appreciated!
The text was updated successfully, but these errors were encountered: