"kenevel" wrote : for example throwing a custom RuntimeException along the lines
of a DataSourceTemporarilyUnavailableException. This could travel up the stack to the
front-end and result in appropriate messages being generated for the system's users.
Why can't you guys handle this in through the application without playing with the JCa
pool Mbeans?
You can have a utility class which will get the connection from the underlying datasource
and if it fails to get the connection due to unavailability of DB this utility class
throws required application exception.
Looks to me you wanted to take care of this scenario
http://wiki.jboss.org/wiki/WhatHappensToJBossIfIRestartTheDatabase
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175649#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...