We recently ran into this problem after a server restart.

As part of our research into why clients were timing out even though
the service was still aparently alive - I had a bit of a scan through
the source (I'm no expert). It appears that superserver tries to (or
used to try to) validate packets before use - hence, if the check is
valid, shouldn't really get to the receive error on the main port:

"SRVR_multi_thread/RECEIVE: error on main_port, shutting down"

Is there an easy answer to this (I thought I'd ask here before
bothering the dev list) - ie the code appears to stop receiving on
the main port without shutting down.

TIA

Max

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...>
wrote:

>
> At 09:55 PM 23/11/2005 +0000, you wrote:
> >
> >I am able to create only 63 concurrent connections to database.

>
> It's a Windows Registry setting ...
>
> The key is
>

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.

> TcpNumConnections
> Key: Tcpip\Parameters
> Value Type: REG_DWORD - Number
> Valid Range: 0 - 0xfffffe
> Default: 0xfffffe
> Description: This parameter limits the maximum number of

connections that

> TCP can have open at the same time.
>

> http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
>
> ./helen
>