Icon View Incident Report

Serious Serious
Reported By: Tiago Ameller
Reported On: 6/10/2009
For: Version 2.02 Build 14
# 3015 Login Attempts that Wait for User Input Do Not Time-Out Properly After the Server Timeout is Reached

I have yestarday dead sessions marked as "connected", with user name at NULL (see attached screen shot). Courious thing is I'm sure client machine was stopped yesterday night and there is nothing pinging server in "I'm still alive" fashion.

After 48 hours of that NULL session staying there, I removed it. EDBMgr has frozen. And worst, server also was hanged.


Comments Comments
Client callbacks, like those used to ask the client for the login information, are waiting indefinitely for a response back from the client. During that time the session is locked on the EDB Server. Therefore, any attempt to remove the session or shut down the server will cause it to continue to wait until the session can be locked, which in this case will be as soon as the user types in their login information and submits it. So, if a client connects a session, but never actually completes the login dialog, then you won't be able to shut down the server or remove the session in question.


Resolution Resolution
Fixed Problem on 6/12/2009 in version 2.02 build 15


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 VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image