Hi,

I would like to remove disconnected sessions for a client (if they are
logging in and there are previous disconnected sessions). I'm not
talking about timing out while inside the client application but when
they physically log out of the application and log in again and there
are still disconnected sessions for that client.

What if I just look at all disconnected sessions for that clients IP
Address and remove them? Are there any pitfalls in doing this? Will this
reset any record locks held by that disconnected session?

Thanks in advance

Jaweed,

<< I would like to remove disconnected sessions for a client (if they are
logging in and there are previous disconnected sessions). I'm not
talking about timing out while inside the client application but when they
physically log out of the application and log in again and there are still
disconnected sessions for that client. >>

If they log out properly, then there shouldn't be any disconnected sessions
on the server for that client.  Or are you talking about a case where the
application was improperly terminated on the client ?

<< What if I just look at all disconnected sessions for that clients IP
Address and remove them?

That will work, although you need to make sure that you only touch
disconnected sessions (current IP address is blank while the last IP address
is populated in the session information retrieved from the server).

<< Are there any pitfalls in doing this? Will this reset any record locks
held by that disconnected session? >>

No, and yes.

--
Tim Young
Elevate Software
www.elevatesoft.com

In an extension to this question:

What can I do to automatically remove disconnected sessions as soon as they appear?
The best thing would be if the server could remove them automatically

Michael

Michael,

> What can I do to automatically remove disconnected sessions as soon as they appear?
> The best thing would be if the server could remove them automatically

Sessions may disconnect simply because the user is talking on the phone
or thinking about what to do next ...it would not be a very good idea
for the server to blow the users work away by default in most cases
(though you can set up the various timing parameters to make it so if
you wish).

Eryk

Michael,

<< In an extension to this question:

What can I do to automatically remove disconnected sessions as soon as they
appear? The best thing would be if the server could remove them
automatically >>

Turn on pinging on all client sessions (TDBISAMSession.RemotePing=True, keep
the RemotePingInterval property the default of 60 seconds).  Then, set the
connection timeout in the database server configuration to 90 seconds.  That
will give the clients enough time to ping the server and keep their
connection open unless the application has been improperly shut down.  In
such a scenario, the longest wait time until a dead client session is
removed is a little under 90 seconds.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I've been struggling with this for a while and thought I understood. So
to make it absolutely clear (to me): wouldn't the longest wait time
until a dead client session is removed in this case depend on the
"deadsessionexpires" serversetting (default 12 hours)?

Regards,
Robert.


Tim Young [Elevate Software] wrote:

> Michael,
>
> << In an extension to this question:
>
> What can I do to automatically remove disconnected sessions as soon
> as they appear? The best thing would be if the server could remove
> them automatically >>
>
> Turn on pinging on all client sessions
> (TDBISAMSession.RemotePing=True, keep the RemotePingInterval property
> the default of 60 seconds).  Then, set the connection timeout in the
> database server configuration to 90 seconds.  That will give the
> clients enough time to ping the server and keep their connection open
> unless the application has been improperly shut down.  In such a
> scenario, the longest wait time until a dead client session is
> removed is a little under 90 seconds.



--

Robert,

<< I've been struggling with this for a while and thought I understood. So
to make it absolutely clear (to me): wouldn't the longest wait time
until a dead client session is removed in this case depend on the
"deadsessionexpires" serversetting (default 12 hours)? >>

Yes, I'm sorry - I didn't go far enough with my explanation and forgot
completely about the expiration times.  When using pinging, you'll also want
to set your dead session expiration time on the database server to a very
low setting, around 15-30 seconds should be fine.  That will ensure that
withing 15-30 seconds of disconnection, the database server will remove the
session completely.

--
Tim Young
Elevate Software
www.elevatesoft.com