Skip to content
New issue

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

NPE in ManagedConnection#internalCommit() on fatal error [JDBC207] #256

Closed
firebird-automations opened this issue Dec 13, 2011 · 7 comments

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Is related to JDBC214

When TestFBMaintenanceManager#⁠testForcedShutdown() is run with test.gds_type=NATIVE, a NPE occurs in ManagedConnection#⁠internalCommit(). The reason is that a fatal error occurs (due to the forced shutdown?), and therefor the gdsHelper is set to null by a call to ManagedConnection#⁠destroy().

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Need to investigate whether a simple null-check is sufficient, or if more work is required.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

assignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ]

Version: Jaybird 2.2 [ 10053 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 2.3 [ 10440 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue is related to JDBC214 [ JDBC214 ]

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Null check was sufficient.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants