So if there is a database server outage, the database nodes are marked as inactive. But if the database server is back up, I still get an exception "No active databases".
The issue is resolved when I restart the web app and it gets a new connection. I read in the documentation that we can have a auto-activation schedule, to detect failed nodes and have them marked as active again. is it possible to do manually ?
And also is it a good idea, to wrap some logic and check if there is 'UncategorizedSQLException' to try to obtain a new connection object and may be mark the node as active again ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So if there is a database server outage, the database nodes are marked as inactive. But if the database server is back up, I still get an exception "No active databases".
The issue is resolved when I restart the web app and it gets a new connection. I read in the documentation that we can have a auto-activation schedule, to detect failed nodes and have them marked as active again. is it possible to do manually ?
And also is it a good idea, to wrap some logic and check if there is 'UncategorizedSQLException' to try to obtain a new connection object and may be mark the node as active again ?