We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submitted by: Derryck welas (welas)
The attachments to database are not closed after a disconnect from a 64Bits running Client.
with a 32bits client to 32 bits database (32bits linux redhat) These attachments are closed normally by the Firebird server.
I tested this with Jaybird full 2.1.3 and jaybirdfull 2.1.6.
my typical connection url in jboss: <connection-url>jdbc:firebirdsql://<<the database>>?no_result_set_tracking</connection-url>
The text was updated successfully, but these errors were encountered:
Fix Version: Jaybird 2.2 [ 10053 ]
timeestimate: 0 [ 0 ]
timeoriginalestimate: 0 [ 0 ]
Component: Wire protocol [ 10050 ]
description: The attachments to database are not closed after a disconnect from a 64Bits running Client.
=>
Component: JDBC driver [ 10053 ] =>
Sorry, something went wrong.
Commented by: @mrotteveel
I am unable to reproduce this issue. I will close this issue; if more information can be provided it can be reopened.
assignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ]
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Cannot Reproduce [ 5 ]
Fix Version: Jaybird 2.2 [ 10053 ] =>
mrotteveel
No branches or pull requests
Submitted by: Derryck welas (welas)
The attachments to database are not closed after a disconnect from a 64Bits running Client.
with a 32bits client to 32 bits database (32bits linux redhat) These attachments are closed normally by the Firebird server.
I tested this with Jaybird full 2.1.3 and jaybirdfull 2.1.6.
my typical connection url in jboss:
<connection-url>jdbc:firebirdsql://<<the database>>?no_result_set_tracking</connection-url>
The text was updated successfully, but these errors were encountered: