Icon View Incident Report

Serious Serious
Reported By: Krisztian Kepes
Reported On: 3/17/2011
For: Version 2.05 Build 4
# 3421 ElevateDB Server Allowing Remote Sessions to Improperly Reconnect to Sessions

One of our customers have problem after the EDB 2.05.4 upgrade. We got mysterious "Cannot lock the database" errors.

These errors are coming non-periodically. For example: in the prev. week we got it, but for 1 week we don't. Today also got it.


Comments Comments
The problem was caused by some changes in 2.05 B4 to allow for more reliable reconnections in instances where a reconnection needs to terminate a running process in a thread before reconnection.

The problem occurs with the following steps:

1) A client's remote session is disconnected from the ElevateDB Server, due to a network issue or the server being restarted.

2) A new session is created with the same session ID on the ElevateDB Server for another completely different client and remote session.

3) The first client now tries to reconnect to its old session, which no longer exists, and the ElevateDB Server allows it to reconnect to the new session that is actually being used by a different client.

The symptoms can range from locking errors to access violations/invalid pointer errors.


Resolution Resolution
Fixed Problem on 3/20/2011 in version 2.05 build 5


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

Image