| Subject | Re: [firebird-support] dropping the connection |
|---|---|
| Author | Nick Upson |
| Post date | 2017-02-24T10:29:56Z |
I remember killing connection via delete from mon$statements with firebird 2.0 or 2.1. Could the fact that it doesn't work for me now be down to upgrading the client install to 2.5?
On 22 February 2017 at 09:44, Mark Rotteveel mark@... [firebird-support] <firebird-support@yahoogroups.com> wrote:Killing connections by deleting from MON$STATEMENTS requires FirebirdOn 2017-02-21 17:32, Nick Upson nu@... [firebird-support] wrote:
> Hi
>
> The problem I'm trying to solve is users leaving inactive db_workbench
> sessions attached to a database while other work is going on by other
> processes, causing a large OIT gap and the consequent problems. The
> solution needs to be automatic and unattended.
>
> db_workbench doesn't have a timeout setting (I asked)
>
> deleting the row from mon$statements doesn't kill the transaction;
> deleting the row from mon$transactions or mon$attachments gives
> "operation not supported"
>
> I could automate a kill of the fb_inetserver process but I would
> rather something with less risk
>
> I figure other people have had this and solved it before, I hope.
>
> currently using firebird 2.1 on centos, shortly moving to 2.5
2.5 and an ODS 11.2 database (so you will also need to backup and
restore the database when migrating to Firebird 2.5!).
Mark