hi @StephanMgaya_6484, good to hear that issues that are reported actually being found by new deployments (even if the error was identified by not actually fixed in the code ! )
So, I'm assuming that you saw errors like this :
java.sql.SQLException: Database lock acquisition failure: lockFile:
[file =/var/run/db/hsqldb/idp.lck, exists=true, locked=false, valid=false, ]
method: checkHeartbeat read: 2015-06-24 21:21:40 heartbeat - read: -4931 ms.
in your log file, right ?
@MarcoFargetta can comment further on the intricate details of why this happens, but I worked around the error by forcing a redeployment of the application (WAR) into the application container (tomcat). The file
/var/run/db/hsqldb/idp.lck is the "lock file" that connects the application to the database (HSQL). My explanation of this is that the old version of the WAR didn't clean up it's connection, and so when the new WAR was deployed, it saw that the connection was locked and couldn't connect. By removing the old WAR, tomcat should clean up the db connections (correct me if I'm wrong, @MarcoFargetta), and allow the new WAR to establish a connection cleanly.
Let me know if this explains things better (and most of all if it actually works !)