Icon View Incident Report

Serious Serious
Reported By: Tony Hall
Reported On: 9/7/2013
For: Version 2.13 Build 3
# 3896 Using an In-Memory Configuration Can Cause a Database Locking Error

I think I have found a locking bug in ElevateDB, although I haven’t been able to find the cause I can reliably reproduce it under very specific circumstances:

- Using in-memory database configuration
- Setting Session property KeepConnections to false
- Accessing the same Database from multiple Processes (this may be a red herring, but only way I have reproduced so far)
- In the process where the error occurs access the same Database in two or more Sessions

An ElevateDB Error #300 occurs when a Session attempts to reopen a Database for a second time (its previous copy having been thrown away due to the KeepConnections property).

Resolution Resolution
Fixed Problem on 9/8/2013 in version 2.14 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