Icon View Incident Report

Serious Serious
Reported By: Arthur Williams
Reported On: 4/11/2018
For: Version 2.27 Build 1
# 4622 ElevateDB Server Does Not Properly Clear Thread Cache When Server's Encryption Password is Changed

EDBServer does not reload settings. If you Stop Server, then Edit Settings, then Start Server, your new settings -do not- take effect.

In addition, while the Edit will not allow you to save with no Encryption password for the system config files etc. it does not insist on a value for ServerEncryptionPassword. After editing ServerEncryptionPassword on the form, you must Close the server and exit it entirely and then launch it again.

The edbsrvr.ini is updated after an edit, but the changes do not take effect unless the server is closed and launched again.

Comments Comments and Workarounds
This issue was caused by the fact that ElevateDB Server threads cache the server encryption settings for performance purposes, combined with the fact that the ElevateDB Server itself caches the threads (based upon the server's thread cache size setting).

The workaround was to restart the ElevateDB Server process when changing the server encryption password after sessions have already connected to the ElevateDB Server using the older encryption password.

The ElevateDB Server also now issues an error if you attempt to modify the server settings and do not include a server encryption password.

Resolution Resolution
Fixed Problem on 4/12/2018 in version 2.28 build 1

Products Affected Products Affected
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial