WAIT a moment--what do you mean? I create the socket in the main thread
pool, accept() there, then postthreadmessage to worker thread, serve, then
shutdown there and then destruct there. Do you say this is buggy? Can you
show me an example?
Regards,
SZ
On 2/23/08, Francois PIETTE <[EMAIL PROTEC
> IQRP pools 1024 closed sockets in a thread context. Could that be the
> cause
> of a problem?
Socket have to be closed from the thread context they have been created.
> Is there any limit on the number of sockets/thread?
I don't know of any limit of socket per thread. The limit is system wide
IQRP pools 1024 closed sockets in a thread context. Could that be the cause
of a problem? Is there any limit on the number of sockets/thread? And in the
worker thread, we have 512 client and server sockets per thread.
Regards,
SZ
On 2/23/08, Fastream Technologies <[EMAIL PROTECTED]> wrote:
>
>
My understanding is that it works on certain types of NAT firewalls.
On these NATs, an external port is mapped to an internal IP:Port.
If this is the case, all packets going to that external port will
go to the internet IP:Port.
Making it work is not that simple though, with the difficult part
bei
It is Win2003 R2 Ent. and has 4GB RAM! Will tell the customer to check for
sockets...
Thanks,
SZ
On 2/23/08, Francois PIETTE <[EMAIL PROTECTED]> wrote:
>
> All sockets are used.
> There is a maximum number of concurrent sockets available for a given
> OS/Config, all applications. You reached th
All sockets are used.
There is a maximum number of concurrent sockets available for a given
OS/Config, all applications. You reached that maximum. Either because of
heavy trafic or because you leak some resource somewhere. Use "netstat -a"
to list all socket, or use TcpView from SysInternals.org
