[jboss-dev-forums] [Design of JCA on JBoss] - Re: Handling fatal JDBC connection exceptions

[adrian@jboss.org]

"jesper.pedersen" wrote : Sounds like a good idea - if you want to take a look see the org.jboss.resource.adapter.jdbc package.
  | 
  | That being said - we are about to start a new implementation of the JCA container where we will keep this feature request in mind.
  | Thanks !

This would be a policy on the connection manager not the adapter.
It would be handled in BaseConnectionManager2::connectionErrorOccurred()
by invoking the pool.

Like Jim, I'd propose three options
* Failing connections only - what we do now
* Idle connections - i.e. just do pool.flush()
* All connections - invoke returnManagedConnection(true) on all the connections in the pool(s) regardless of whether they are in use or not.

I don't like the last one because unless it is a real database failure rather than
a transient failure on one connection, you're failing far more transactions than you should.
It would be better to let the ExceptionSorter trap whether there are real failures
to those in use connections.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168167#4168167

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168167