A client of mine recently had some problems with a JDBC app when database connections became 'hung' for one reason or another - database restart, network failure, etc. Their code was not robust enough to toss out a bad Connection and establish a new one. This led me to wonder how JBoss handles this, if at all. Let's say that there's a temporary network failure that hoses all of the DB connections in a pool. Furthermore, let's say that the JDBC driver isn't the greatest, and it doesn't re-establish a Connection, instead it either hangs when the connection is used or throws a SQLException.
Does JBoss have any way of detecting and/or handling dead Connections? I could imagine, for instance, the connection pool logic doing some sort of a connectivity test before handing out a Connection. This would seem to me to be a very "real world" sort of problem. I'm wondering if it's just assumed that JDBC drivers will do the necessary recovery. Apologies if this is in a FAQ. -Eric ETA Associates, Inc http://www.ultracode.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
