Re: [xSocket-develop] xSocket Server and TIME_WAIT

[Gregor R. <gre...@go...>]

Hi Ahmad,

this is common problem. If plenty of connections will be established and
destroyed within a short period of time, the server will run into the Too
Many Open Files error. This is caused by the OS.

The Too Many Open Files support pattern (
http://support.bea.com/application_content/product_portlets/support_patterns/wls/TooManyOpenFilesPattern.html)
describes this problem and how to handle it. For windows take also a look
into Tuning Windows (
http://publib.boulder.ibm.com/wasce/V1.0.1/en/Tasks/Tuning/Windows.html)

If you can controlthe clients, they should use persistent connections by
performing repeated request. On the client-side xSocket supports persistent
connections by the ConnectionPool class.

Gregor


2008/5/8 Ahmad Zurkarnain <to...@gm...>:

> Hello,
>
> I'm using xSocket 1.x server and currently we have been bombarded with many
> request. When I do netstat -na, there are a lot of connections in TIME_WAIT
> state. My concern is that our application may run out of connection/socket
> soon or later. Is there a way using xsocket to solved this?
>
> Thank you.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> xSocket-develop mailing list
> xSo...@li...
> https://lists.sourceforge.net/lists/listinfo/xsocket-develop
>
>