Subject | Classic Server & not correct closed connections |
---|---|
Author | gbehnke2000 |
Post date | 2004-11-10T09:11:08Z |
Dear Members,
to improve the performance in conjunction with a Multiprocessorsystem
we changed successfully from Superserver to Classicserver. We have no
problems with one exception:
In the case that a client dos'nt close correctly (might be trough a
crash) the db connection, the fb-process "FB_inet_server.exe" keeps
open. Therefore from time to time (approximately every four weeks) we
shut down the server to close all unnecessary connections.
Is there another way to find out what fb processes can be killed
respectively for the future of the development of fb can this be done
automatically from fb ?
Many thanks
Gerhard Behnke
to improve the performance in conjunction with a Multiprocessorsystem
we changed successfully from Superserver to Classicserver. We have no
problems with one exception:
In the case that a client dos'nt close correctly (might be trough a
crash) the db connection, the fb-process "FB_inet_server.exe" keeps
open. Therefore from time to time (approximately every four weeks) we
shut down the server to close all unnecessary connections.
Is there another way to find out what fb processes can be killed
respectively for the future of the development of fb can this be done
automatically from fb ?
Many thanks
Gerhard Behnke