Internal Database Fails to Log After SparkEngine Shutdown (4047822)

If the SparkEngine fails to shutdown gracefully, the SparkEngine process will have to be manually killed. If the process is killed and the embedded database still contains results, take special care in restarting the SparkEngine. A condition exists where the embedded database becomes corrupt, and as a result, none of the entries contained in the internal database will be written when the SparkEngine is started again. Therefore, it is quite important that a test message is sent through the system to verify logging after the SparkEngine has been restarted. If the SparkEngine logs nothing upon submission of this test message, stop the SparkEngine again and move or remove the /tmp/db directory and start up once more. The /tmp/db directory will be automatically recreated.

This issue is fixed in 6.0

Please refer to the text above