Try "touching" the *-ds.xml file. That will update the last modified timestamp which will cause the app server to redeploy the datasource.
Peter, is there any more automatic recovery available? I just encountered a similar problem. We have many Jboss AS instances connecting to a central DB. Because of a full disk the DB (Postgres) stopped working and after resolving the problem the DB had to be restarted.
The problem was that none of the Jboss instances were able to connect anymore after this restart and they all had to be restarted manually. This is rather tedious to say the least. Touching the *-ds.xml file reliefs this pain only a little.
I found this other thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4158716
It seems that if you have valid connection checker, then basically the redeployment of the datasource would not really be needed. Sure, it might still be better to redeploy instead of waiting for every connection to have thrown an exception, but eventually the pool *should* recover automatically. Only. clearly it doesn't (or it doesn't always). The topic starter has a valid connection checker configured, so if I understand correctly those connections should have been closed and re-opened, shouldn't they?
Hello. Would you mind to show configuration of your *-ds. xml file? I have configured my datasource file with suggested steps but Jboss doesnot reconnect when mysql database restart. Here is content of my -ds.xml file:
<check-valid-connection-sql>SELECT 1 FROM sysobject</check-valid-connection-sql>
I am newbie to JBoos but need to make this work. Thank you all for any help.