Subject | Re: Classic Server leaves "ghosts" connections behind |
---|---|
Author | Eduardo A. Salgado |
Post date | 2005-09-24T22:45:30Z |
--- In firebird-support@yahoogroups.com, "Adam" <s3057043@y...> wrote:
correctly, we will have reached some limit and will have to end the
process of those "ghost" manually.
any CPU time anymore and have not for quite a while. Is there a way
to tell?
how does FB know the connection is turned off? These I believe are
the "ghosts" still thinking that there is a connection but really the
app that called the FB has been disconnected and not really Closed.
Not sure if that is the way Citrix handles it.
Thanks!
-Eduardo
> Hang on a tick. Are they really "ghost" connections, or are theyThis is what I believe.
> connections created by sessions that are still technically active
> but no-one is connected to it?
> If they are connections with no active transactions running, thenare
> unless you are worried about the 1024 connection limit, then they
> not using substantial resources.Yes, but,... at some time, if they are not terminated or disconnected
correctly, we will have reached some limit and will have to end the
process of those "ghost" manually.
>If they do contain activeHow can I tell? I call them "ghosts" because they do not seem to use
> transactions, then you have a problem, because they are probably
> keeping old record versions interesting.
any CPU time anymore and have not for quite a while. Is there a way
to tell?
>We automatically end the sessions of users who have disconnected forIn our case our user has 6 hour set. But, when they are disconnected,
> over 30 minutes.
how does FB know the connection is turned off? These I believe are
the "ghosts" still thinking that there is a connection but really the
app that called the FB has been disconnected and not really Closed.
Not sure if that is the way Citrix handles it.
Thanks!
-Eduardo