Subject | Re: [ib-support] Re: killing a running connection |
---|---|
Author | Martijn Tonies |
Post date | 2002-11-28T07:40:12Z |
Hi,
From my (limited) experience in killing the client application -
IB/Fb will kill the connection only when it's already returning data
to the client - or at least, it detects it much faster than when
running a heavy UPDATE or something like that.
Martijn Tonies
Firebird Workbench - the developer tool for Firebird
http://www.upscene.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
From my (limited) experience in killing the client application -
IB/Fb will kill the connection only when it's already returning data
to the client - or at least, it detects it much faster than when
running a heavy UPDATE or something like that.
> Ivan,With regards,
>
> > you can kill the application -
> > FB server will notice it and cancel the query.
>
>
> I do use a TCP/IP connection.
>
> However, this morning killing the client application that started the
> the heavy task did not release the server: it went on working and
> leaving all the other clients on wait, at least for several seconds.
>
> Maybe I was too impatient and should have waited longer ?
>
> I mean: how long does it take to FB to realize that a TCP/IP
> connection is lost so that all the tasks belonging to the dead
> connection can be stopped ?
Martijn Tonies
Firebird Workbench - the developer tool for Firebird
http://www.upscene.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."