Icon View Incident Report

Serious Serious
Reported By: Terry Swiers
Reported On: 6/30/2021
For: Version 2.34 Build 3
# 4833 Per-Minute Job Scheduling Can Cause Unhandled Thread Errors and Crash the ElevateDB Server

I have some scheduled jobs that produce an application error in the Windows event logs. The two jobs (Test and Test1) in the config are trivial and nonsensical, but show the issue.

Steps to Reproduce:

1. Copy the edbsrvr.exe server engine and the config to an empty folder. The config is set to use C:\Temp folder for the configuration file and temporary files.

2. Start the server engine as a regular application.

3. Open up EDB Manager. connect to this instance, and watch the LogEvents table.

4. When the log events table shows the second Execute Job entry for the Test job, open up the Windows events viewer. In the Windows Logs \ Application section, you will see both an application error and an appcrash entry for edbsrvr.exe.

After the error occurs, both jobs stop being executed.

This example only throws an entry into the Windows log events table. I have a client with multiple non-trivial jobs, that exhibits similar behaviour but in this case the server engine service terminates.

Comments Comments
There was an issue with the job execution that was re-vamped in 2.34 that would cause locking exceptions in the job monitoring thread that would crash the server (unhandled exceptions trying to escape a thread).

Resolution Resolution
Fixed Problem on 7/2/2021 in version 2.35 build 1

Products Affected Products Affected
ElevateDB Additional Software and Utilities
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