We are using a SQL Server database as the journal of our EM Server 5.8.2. It seems that if the server loses connection (for example if the database restarts), it can not connect again without an explicit restart of the service.
Do you confirm ?
Would it be possible to retry periodically and when connection is up, switch back automatically from the in memory "safe" mode to the nominal mode ?
I suppose that this restart is mandatory because of this in memory mode in case there's a problem, not able to switch back to the normal way ?
Hi,
Could you please elaborate on which specific service needs to be restarted?
Do you mean that admins must manually click the Retry link in the journal through the WebUI?
We had to restart the easymorph service on the server. The "try again" link did not work.
I was thinking that maybe the easymorph service on the server would automatically try periodically to reconnect to the sql server of the journal, but that's not what is happening.
Please send us the Server debug logs for the SQL server's inactivity period. Including the logs before and after clicking the "Try again" link would also be helpful.