Hi
In our current solution ,We are using a DB Failover mechanism when our Primary DB server is down (configured by “Add Failover” in the DB connections as if Primary DB downs , then it fails over to Secondary DB and if the second downs ,fails over to Primary) although that this works we always needs to restart tomcat when a connection is reestablished to the primary server for the app to detect this , more importantly if both servers go down even if they come back again we are unable to detect this so nothing is written on the DB even though that both servers are up unless we restart tomcat.

So, suggest us how can we change the code so it works without a tomcat restart (bearing in mind that the current architecture is used many places in the code so if possible we would like to avoid reengineering this).

Avaya OD Version : 6.0

Thanks
Kasthoori.J

Take a look at my comment on this post:

http://www.devconnectprogram.com/forums/posts/list/46.page

It has the same configuration that you need to fix this problem.

Hi
Thanks for the answer !
We will try the suggestion. but we are generating many files (various app) and we have regular deployments .Can we add the settings somehow prior deployment so that when the context files are generated already contain those?

Regards
Kasthoori

In the data source editing dialog, there is a drop-down section at the bottom that allows you to set validationQuery and testOnBorrow parameters. These settings will be updated in the context file when you do the export. Usually these 2 parameters are adequate for reconnecting in case of network issue. If these 2 parameters don't work, then you would have to manually add the other 2 parameters.