Gents,
Would it make sense to offer an option to destroy all connections in the pool upon
encountering a fatal exception? Currently a catastrophic failure of the database can
cause all connections in the pool to become useless. Without a VCC (or SQL) configured,
this means that each connection in the pool will be used one further time before it throws
a SQLException which, when determined as fatal, will cause the connection to be
destroyed.
If we offered such a setting, we could avoid this scenario without even having to do
proactive validation. The setting would of course be optional and default to the current
behavior.
Thoughts?
-Chris
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158510#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...