At 11:00 PM 27/03/2006, you wrote:

>The server process crashed. Enjoy!

Not with this scenario. Glebas wrote:

> Which, in turn, leads to other clients (but not all!) occasionally
> receiving the same message until the server is rebooted.

But if this is Superserver, and you have the scenario where some of
your users are crashing out of their applications while the server is
waiting for more *network* packets to fill a large *database* packet
(like a blob or a large SQL statement), then everyone else who is
waiting for something will just wait...and wait... for packets that
never come...until some will just time out because the client side of
the connection thinks the server has gone. (This problem is fixed in
Fb 2.0, btw.)

You'll get similar behaviour if there is a NIC or router in the
network with a faulty connection that drops out during a packet
wait. Sometimes, too, people load up under-resourced Windows
networks with lots of shares and big print queues that hog all the
bandwidth and cause traffic jams.

And there are more....like the DHCP service swooping around the
network killing connections that have stayed idle too long, and
reassigning the IP address to a different network node...that's
another kind of forcible close that can happen.

./hb