Hello,

In my small client server application I open a session which shows up on the monitoring screen of the server.
I then disconnect the session and the screen dutifully displays the IP address of the session
followed by (Disconnected)

I would like to know why the EDBSession1.Close;doesn't just go away but remains visible with the word Disconnected
after it. Since this is within the eval version of EDB, these disconnected sessions count toward the
max 5 sessions allowed and this is limiting my testing.

Am I forgetting to do something? This behaviour remains even if I close the session. i.e.

EDBSession.Connected := false;
EDBSession.Close;

I'm using 2.04 build 4

Thanks to all

Oliver

Oliver,

> Am I forgetting to do something? This behaviour remains even if I close the session. i.e.

Open the EDBServer GUI, stop the server, click on "Edit Server Options"
and open the tab "Sessions". There you will find:

"Dead Session Interval" and
"Dead Session Expiration Time"

You can adjust both to a value that fits your needs.

Regards Uli

Uli,

Thanks for pointing that out. I do note though that without changing any of these parameters, when I close
out my application, the session shown on the server status window disappears entirely. It does not
remain with "(disconnected)" shown next to it. Having the session disappear as if the application
had closed is the behavior I am looking for.

Thanks

Oliver


Uli Becker wrote:

Oliver,

> Am I forgetting to do something? This behaviour remains even if I close the session. i.e.

Open the EDBServer GUI, stop the server, click on "Edit Server Options"
and open the tab "Sessions". There you will find:

"Dead Session Interval" and
"Dead Session Expiration Time"

You can adjust both to a value that fits your needs.

Regards Uli

Oliver,

<< Having the session disappear as if the application had closed is the
behavior I am looking for. >>

Not sure if that's possible.

Tim may correct me, but in my understanding a session is considered as
dead when it has been disconnected by the server engine for some reason
and not been reconnected.

On the other hand a "regular" disconnection on the client side does not
produce a dead session. That's why it's not displayed in EDBServer GUI
any more.

Regards Uli

Oliver,

<< In my small client server application I open a session which shows up on
the monitoring screen of the server. I then disconnect the session and the
screen dutifully displays the IP address of the session followed by
(Disconnected)

I would like to know why the EDBSession1.Close;doesn't just go away but
remains visible with the word Disconnected after it. Since this is within
the eval version of EDB, these disconnected sessions count toward the max 5
sessions allowed and this is limiting my testing. >>

I'm not sure what's going on, but your client machine is not cleanly
disconnecting.  I just tried the following here:

procedure TForm1.Button1Click(Sender: TObject);
begin
  EDBSession1.Connected:=True;
end;

procedure TForm1.Button2Click(Sender: TObject);
begin
  EDBSession1.Connected:=False;
end;

with a simple remote TEDBSession component, and the connect/disconnect works
fine.

--
Tim Young
Elevate Software
www.elevatesoft.com