[stunnel-users] Stunnel Problem - 935 Maximum connections onWindows

[Lund, Claus]

I recently did some work on an app where a problem came up regarding the
number of threads on a Windows system... I wasn't deeply involved in
that part of the code so don't have all the details. It was caused by
the default stack size used by the linker. I believe the default was 1
or 2 MB. So, once enough threads were created to use up all the memory
then things started failing. The issue was "fixed"/worked around by
lowering the stack sized.
I don't know if this is the case here ... but if it is and you want more
details then I may still be able to get my hands on some of that code.

-Claus


-----Original Message-----
From: stunnel-users-bounces at mirt.net
[mailto:stunnel-users-bounces at mirt.net] On Behalf Of Michal Trojnara
Sent: Wednesday, February 06, 2008 4:09 PM
To: <stunnel-users at mirt.net> <stunnel-users at mirt.net>
Subject: Re: [stunnel-users] Stunnel Problem - 935 Maximum connections
onWindows

On 2008-02-06, at 19:06, Iain @ Mobile777 wrote:
> We have even tried running Stunnel separately on a Linux distro (FC4),

> with even less positive results.

That's strange.  I was testing stunnel with over 10k connections on 
Linux 2.6.18.
You just need to make sure ulimit values (e.g. file descriptors) are 
high enough.
http://stunnel.mirt.net/perf.html

>  _beginthread: Exec format error (8)
> Connection rejected: create_client failed

Fascinating.  What is the resource utilization (memory, threads, etc.)?
It looks like there's a limit of 1000 threads on your Windows 2003 
server.

Best regards,
	Mike (the author of stunnel)

_______________________________________________
stunnel-users mailing list
stunnel-users at mirt.net
http://stunnel.mirt.net/mailman/listinfo/stunnel-users