description: If an exception occurs during a statement prepare, and that exception is not of type GDSException, then a subsequent close() of the connection does actually close the connection. A subsequent attempt to drop the database (as done during automated tests) will then result in an exception:
org.firebirdsql.gds.GDSException: lock time-out on wait transaction
object D:\DEVELOPMENT\PROJECT\JAYBIRDECLIPSE\CLIENT-JAVA\FBTEST.FDB is in use

Adding the following catch block to the FBPreparedStatement constructor solves this issue
catch (Exception e) {
notifyStatementCompleted(false);
throw e;
}

However, it would be good to further investigate why this blocks closing the physical connection and if there are more resource leaks like this.

=>

If an exception occurs during a statement prepare, and that exception is not of type GDSException, then a subsequent close() of the connection does not actually close the connection. A subsequent attempt to drop the database (as done during automated tests) will then result in an exception:
org.firebirdsql.gds.GDSException: lock time-out on wait transaction
object D:\DEVELOPMENT\PROJECT\JAYBIRDECLIPSE\CLIENT-JAVA\FBTEST.FDB is in use

Adding the following catch block to the FBPreparedStatement constructor solves this issue
catch (Exception e) {
notifyStatementCompleted(false);
throw e;
}

However, it would be good to further investigate why this blocks closing the physical connection and if there are more resource leaks like this.

Link: This issue is related to JDBC214 [ JDBC214 ]

Version: Jaybird 2.2.3 [ 10510 ]

Version: Jaybird 2.2.2 [ 10480 ]

Version: Jaybird 2.2.1 [ 10474 ]

Version: Jaybird 2.2 [ 10053 ]

Version: Jaybird 2.1.6 [ 10285 ]

Fix Version: Jaybird 3.0 [ 10440 ]

Version: Jaybird 3.0 [ 10440 ] =>

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

resolution: Fixed [ 1 ]

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