Home.... | log in.... | Pub my question! | Sign-up....
Java-index >> Web & Directory Servers >> Portal Servers

How to eliminate 'CLOSE_WAIT ' in portal server and gateway..

We have iPS SP2HP4 with gateway and server in different machines. Always its increasing the CLOSE_WAIT parameter in gateway and server. Whenever it reaches certain value(app.30 to 40 in server and 15 in gateway) the gateway and server are not responsing properly and after some time portal become down. After restarting again its working fine. This situation is frustating. Is there any way to clear or decrease the CLOSE_WAIT value without restarting the server. Please let me know if anyone knows how to solve this situation and appreciate for any help.

[569 byte] By [708896] at [2007-11-25 4:35:33]
«« "Gateway Error"
»» My netlet provider detects Netscape though I'm using Internet Explorer.
# 1

To clean up the CLOSE_WAIT sockets more efficiently , you can increase the Gateway threads.

GO to Admin Console | Gateway Management | Manage Gateway Profile | select "Show Advanced Options" in the bottom of the page and change the following tuning parameters.

1) Increase the value of "Maximum Thread Pool Size". The default is 200, and it can be increased to 800.

2) Also increase the Gateway Timeout. The default is 120000. This can be increased to 125000. Then click Submit

The better cleaning up of the CLOSE_WAIT sockets left is fixed in SP3 release.

708766 at 2007-6-29 2:47:51 > top of Java-index,Web & Directory Servers,Portal Servers...
Portal Servers

Web & Directory Servers New Topic

Web & Directory Servers Hot Topic

Web & Directory Servers

All Classified