The problem we facing is to close the bad database connection due to network failure or whatever other reasons instead of returning it back to pool. I know glassfish DataSource has api to mark the connection bad. However, in EJB 3 context, all those connection/datasource are hidden. I tried "fail-all-connection=true" in pool configuration and it didn't work as expected. We're using glassfish 2.1 btw. Does anyone else meet same problem? What's the available solution or workaround?
[Message sent by forum member 'greenplum' (greenplum)]
http://forums.java.net/jive/thread.jspa?messageID=353491