Hi,

a) PROBLME 1: Dead Client Connection
=======================================================================
we use Firebird 1.5.3 (classic server) to drive our websystem an we have
problems with dead client connections that hold transaction open.

Our System is a Windows 2003 Standard Server (SVP1) with 2 GB RAM and 2
Processors (Hyperthreading 4 Processors).

The Main Database have a size of 6 GB. The database are used from an
second server (Webserver) with a 1 GB Ethernet line, and additional by
connections by Internet Access.

Normally we have 50 to 100 open connections for the database, mainly
from the Webserver.

The problem is (seemed to be) that connections that are broken because
the client are disappeard (Internet Line broken) are still hold open on
the DB Server.

I can see this because the fb_inet_server.exe of this connection are
stay in memory an never disappears. Additionnal I can see with "netstat"
that the connection are still open.

This connections are open also if I close the listener process. This
connections are open for days and weeks if wie don't kill them by
taskkill or reboot the system.

This connections cause that transaktions are hold open and the distance
between the active and oldes transaction are grow and grow.

I try a little research an found out 2 potential solution...

---

a) One is in firebird.conf the parameter "DummyPacketInterval"... but
also there is a warning:

# DO NOT USE THIS OPTION. It may hang or crash Windows on the client
side as
# explained here: http://support.microsoft.com/default.aspx?kbid=296265
# or may not prevent eventual inactive client disconnection for other
OS.

The default Value ist 0 (disable), Have anybody expericence with
DummyPacketInterval and the problems that this should cause ?

---

b) Settings KEEPALIVE in Windows.

Background is this document:

http://ibdeveloper.com/issues/issue-1-sep-1-2005/using-keepalive-sockets-to-detect-and-release-hung/

On our system nothing is set and because of this the the default value
(2 Hours) are (should) used. But the dead client connections are also
active it they are older then 2 hours.

Have anybody experience with this settings?

---

b) PROBLME 2: Growing memory consumation
=======================================================================
Additional we notice that the size of the pagefile grows and grows by
the time. But we don't see any process that use this memory. Also if we
stop all processes the memory use (page file) don't becomes smaller.

We assume that this have anything to do with the "dead client problem".

---

We change 3 month ago from superserver to classicserver. The problems
starting with this move. With superserver we never have problems (only
the SMP Issu)

Have anybody expericence with this problems and a solution for the "dead
client connections" Issue?

with best regards

Nils Bödeker

_________________________________

Verlag Eugen Ulmer
Datenbanken und IT-Entwicklung

Nils Bödeker
Bürgerwohlsweg 7
D-28215 Bremen
Germany

Tel: +49 (0)421 - 3795020
Fax: +49 (0)421 - 3795021
Mobil: +49 (0) 172 - 7468066

nboedeker@...
www.ulmer.de / www.nbsoft.de


yahoo ID: nilsboedeker
Skype ID: nilsboedeker
ICQ ID: 206474523