-----Message d'origine-----
De : François Piette [mailto:francois.pie...@overbyte.be] 
Envoyé : vendredi 17 août 2012 21:32
À : 'dushy...@intellectsoftwares.com'
Objet : RE: CreateWindowEx failed error in TWSocket

By default, Windows is limited to 10000 window handles globally. You
probably hit that limit.
I don't know which ICS version you are using but I suspect you are using an
old one because ICS-V7 is sharing the same window (a hidden window used only
for his message queue) and you can have much much more connections without
tweaking Windows parameters.

It is also possible that you don't free the socket after use and after
sometimes you have consumed all Windows resources. Use madExcept4 and
FastMM4 to help you find the leaks, if any.

Please use the support mailing list to further discuss this topic. See
"support" link at my website for details.

The author of the freeware multi-tier middleware MidWare The author of the
freeware Internet Component Suite (ICS) http://www.overbyte.be

-----Message d'origine-----
Envoyé : vendredi 17 août 2012 16:13
Objet : CreateWindowEx failed error in TWSocket

Hello Sir,

I have used your ICS-ver6 ->TWSocketServer component and I am very satisfied
with the performance of the socket.

I use TWSocketServer component for my server application which ideally has
around 1000 to 1500 Active client connections, and around 10,000 total
connections in a day.

I have created a .net library(dll) of your component from Delphi and using
the same in c# .Net 2010. Lately i have started facing the problem of
"CreateWindowEx failed". After this exception, no new connections to the
server are possible. The entire machine goes into a hung state and it has to
be restarted. Sample exception log is as follows for your reference.

Source          : OverByteIcs
Method          : AllocateHWnd
Date            : 2:52:43 PM
Time            : 8/17/2012
Computer        : isp1server1
Error           : CreateWindowEx failed
Stack Trace     : at OverbyteIcsWndControl.TIcsWndHandler.AllocateHWnd()
    at OverbyteIcsWndControl.TIcsWndControl.AllocateHWnd()
    at OverbyteIcsWSocket.TCustomWSocket.AllocateSocketHWnd()
    at OverbyteIcsWSocket.TCustomWSocket..ctor()
    at OverbyteIcsWSocket.TCustomSocksWSocket..ctor()
    at OverbyteIcsWSocketS.TWSocketClient..ctor()
    at OverbyteIcsWSocketS.TWSocketClient.@MetaTWSocketClient.@Create()
    at OverbyteIcsWSocket.TCustomWSocket.Do_FD_ACCEPT(TMessage& msg)
    at OverbyteIcsWSocket.TCustomWSocket.WMASyncSelect(TMessage& msg)
    at OverbyteIcsWSocket.TCustomWSocket.WndProc(TMessage& MsgRec)

I have noticed that this problem occurs only on the server where no.  
of total connections are in the range of 9,000 to 10,000. The same server
applications runs on other servers too, with an approximate load of 600-700
active connections without any problem.

I would be grateful to you if you can assist me on the above mentioned

Thanking You in anticipation.

To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to