How do I know if I need JDBC Verify?
Like any data source, the configuration database that Yellowfin runs on top of can experience connection problems. If you are experiencing "connection closed" or "connection dropped" errors in the JDBC.log file such as the error below, then it may be worth enabling JDBC Verify:
2017-04-05 19:08:38 WARN: Execution problem occurred when clearing warnings: java.util.concurrent.ExecutionException: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
The JDBC Verify property tells Yellowfin to test the configuration data base connection frequently. If the connection is closed, Yellowfin will attempt to re-open it. This prevents you from having to manually reset this connection.
How do I enable JDBC Verify?
To enable JDBC verify we need to add the following property to the web.xml file. This can be found in youryfinstall/appserver/webapps/ROOT/WEB-INF/web.xml
In order for this to take effect, you will need to restart Yellowfin.
<init-param> <param-name>JDBCVerify</param-name> <param-value>true</param-value> </init-param>
It is important that you place this in the same location as the rest of the JDBC connection parameters and indent appropriately, the final result should look like:
How do I know if I have enabled this correctly?
Once you have enabled this setting and restarted Yellowfin, you will see that the verify connections tag in the JDBC.log says "true"