RE: CLOSE_WAIT issue

[Xiong Shawn Zhang]

Robert,   Thank you very much for your reply.   Actually, the IP address each CLOSE_WAIT tcp connection points to is a client IP, so I assumed it is the issue related to the web services and the clients. For clients, we can’t require them to set timeout (even though there is such a parameter). So I am wondering if we have some timeout setting on the service side as well, which may solve our problem.   Thanks a lot for your help.   Shawn   From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 4:34 PM To: axis-user@ws.apache.org Subject: Re: CLOSE_WAIT issue   Are you sure this is axis creating this issue? A lot if people use axis 1.x and tomcat without any such problems. What does happen, however, is that the java NIO library does have some bugs that I've personally seen create nasty close_wait issues. If you're app or libraries do anything with NIO, I'd do a search in the bug parade. Some bugs are listed as closed, but the comments in the reports keep comming. HTH, Robert http://www.braziloutsource.com/ On 5/9/06, Xiong Shawn Zhang < [EMAIL PROTECTED]> wrote: Hi,   There is an Axis web services app running in our production boxes, and the web container used is pure tomcat 5.0.25 (no Apache server used). We are now having service hanging issue. I checked the log files, everything normal (no exception). However, I found we have lots of CLOSE_WAIT tcp connections hanging, which related to the clients. Is there any body knows if there is an AXIS/TOMCAT configuration, or function, which could be used to force the connections to be closed (e.g. timeout)? Your help is highly appreciated.   Shawn