View Incident Report

Serious

Reported By: Rob Grundy
Reported On: 8/7/2017
For: Version 4.44 Build 2

# 4563 Dead Sessions that are Still Processing a Request Can Cause Problems Removing Other Dead Sessions

We've been getting reports from a customer of repeated crashes of their system - which have required a database server restart to cure. I've installed the latest 4.44b2 debug version of the database server on their machine to try to capture what is causing the issue.

...Private details...

The bigger issue (as it's one we've seen a few times but never been able to find a method to recreate) seems to be the # 10243 Cannot lock the session error, as this leads to sessions in the server not clearing out correctly and the server hitting the session count limit. It only resets after a proper re-start of the database service.

Comments

The cause of this issue was a multi-threading bug in the client application, but the end result was that a messed-up session on the DBISAM Database Server would block the server from removing any other dead sessions because it would not skip over a dead session if it could not be locked (the session was locked because it was still processing a request).

Resolution

Fixed Problem on 8/8/2017 in version 4.44 build 3

Products Affected

DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard
DBISAM ODBC Standard with Source
DBISAM ODBC Trial
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap