[EMAIL PROTECTED] wrote:
> i've dynmically added a XADataSourceLoader MBean during program
> execution, and i was testing the behavior if the connection failed.
> an exception is thrown inside jBoss, but it isnt' returned to my
> application. (the exception is shown below) unless i've missed
> something, i correctly handle a SQLException in
EMEDBAdapaterEJB.ejbCreate()
> any ideas why this is happening?
Well, from the stacktrace, it looks like you're not catching the
SQLException. Can you post the code?
> also, what should be the behavior of jBoss is a connection is lost?
> is there a built-in recovery mechanism or a facility to add an
> application level recovery mechanism?
The idea of throwing the SQLException if there's a problem in
startService is so that the pool will be shut down if there's a problem.
I'm too lazy to look it up right now, but the code that normally calls
startService etc on the MBeans will catch the exception and kill the MBean.
What really interests me about this is why you would want to create a
new connection pool in ejbCreate. There's no way that's going to be
portable.
Toby.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
