Icon View Incident Report

Serious Serious
Reported By: Ulrich Doewich
Reported On: 7/27/2011
For: Version 2.05 Build 10
# 3491 Closing Down a Connection In Response to a "Connection Lost" Error Does Not Work with Active Filters

I've just run into the same(?) issue we discussed last year in June: after receiving a #1101 I attempt to call DbSession.Close which results in my app freezing...

I do have StayConnected := False in DbSessionRemoteTimeout, and Continue := False and StopAsking := True in DbSessionRemoteReconnect.

I'm simulating the problem by using my client to log into the server, then I restart the server service via Windows Services control app. When I now try to re-connect I first get the exception and then the freeze on trying to close the open session.

A bit more detail: same as last year's problem, it only happens when I had my log browser window open, which applies filters on two tables. If I don't open the log browser, a server restart is handled gracefully (i.e. my client displays an error prompt) and the client is still usable. Once I have opened the log browser I get a "#9999 Operation aborted" exception when I try to call DbSession.Close after receiving the #1101 exception... the next DbSession.Close call after that (i.e. when I try to close the client) causes an endless loop of timeouts and EEDBAbortExceptions with message 'The connection to the server at 'cronos' has been lost ('The reconnection was cancelled')'.


Comments Comments
The problem was caused by the filter dropping code for the TEDBDataSet causing a silent abort when it shouldn't have been.


Resolution Resolution
Fixed Problem on 8/12/2011 in version 2.05 build 11


Products Affected Products Affected
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image