Subject | Re: [firebird-support] Auto connection timeout |
---|---|
Author | unordained |
Post date | 2010-07-13T19:09:31Z |
---------- Original Message -----------
From: "Chee Yang" <cychau@...>
I'm not seeing an option for that. You can read for yourself what is available in
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_config or look in the
comments in your copy of firebird.conf, particularly at the section for
DummyPacketInterval, but that doesn't look hopeful.
Do you have a stateful firewall [ http://en.wikipedia.org/wiki/
Stateful_firewall ] you could set this sort of rule up on? How frequently
Firebird sends keepalive packets could affect how you write such a rule (no-
packets-seen-for-X-minutes?)
Another option might be to run a scheduled job on the server, joining between mon
$attachments and mon$transactions (each has a timestamp field indicating when it
was started), trying to identity connections that have no active transactions?
But there doesn't seem to be a good way to tell how recently a given connection
started or committed a transaction that is now no longer in the mon$transactions
view, and if all transactions are extremely short-lived, each time you check, you
may think the connection is idle, when in fact you've just barely missed seeing
it do something. Tricky.
-Philip
From: "Chee Yang" <cychau@...>
> Can we configure Firebird server so that after 6 hours of idle for the------- End of Original Message -------
> connection, firebird server will close the connection at server side.
> Chau, Chee Yang
I'm not seeing an option for that. You can read for yourself what is available in
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_config or look in the
comments in your copy of firebird.conf, particularly at the section for
DummyPacketInterval, but that doesn't look hopeful.
Do you have a stateful firewall [ http://en.wikipedia.org/wiki/
Stateful_firewall ] you could set this sort of rule up on? How frequently
Firebird sends keepalive packets could affect how you write such a rule (no-
packets-seen-for-X-minutes?)
Another option might be to run a scheduled job on the server, joining between mon
$attachments and mon$transactions (each has a timestamp field indicating when it
was started), trying to identity connections that have no active transactions?
But there doesn't seem to be a good way to tell how recently a given connection
started or committed a transaction that is now no longer in the mon$transactions
view, and if all transactions are extremely short-lived, each time you check, you
may think the connection is idle, when in fact you've just barely missed seeing
it do something. Tricky.
-Philip