> 1. jaybird is not emitting a ConnectionErrorEvent to registered
> ConnectionEventListeners when this error occurs. I'd expect that
> jaybird should emit such an error whenever you try to use a dead
> connection.

Looks like this is the case. I checked the source and the
isc_network_error (the one that is generated when IOException happens
during socket access) is not in the list of fatal errors.

I have committed the fix to the CVS to Branch_2_1 and to HEAD.

Andrew, can you recompile the code from the CVS and try it on your site?
Below is the patch for the case you don't want to bother with CVS.

Roman

Index: FatalGDSErrorHelper.java
===================================================================
RCS file:
/cvsroot/firebird/client-java/src/main/org/firebirdsql/jca/FatalGDSErrorHelper.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- FatalGDSErrorHelper.java 9 Oct 2005 17:26:31 -0000 1.1
+++ FatalGDSErrorHelper.java 13 Mar 2007 05:32:42 -0000 1.2
@@ -64,6 +64,7 @@
* This list has been kindly reviewed by Ann Harrison, 12/13/2002
*/
static final int[] FATAL_ERRORS = new int[] {
+ ISCConstants.isc_network_error,
// ISCConstants.isc_bad_db_format, //probably not a firebird db
// ISCConstants.isc_bad_db_handle, //couldn't get a connection
// ISCConstants.isc_bad_dpb_content, //couldn't get a connection