I ran 30,000 test calls in 5 minutes against my Linux Axis server, and there was a bunch of CLOSE_WAIT sockets, but they eventually disappeared, probably when the finalizer ran. It's possible that the web container or JVM doesn't actually close() the native socket until it's finalized.
On 12/12/05, Michael Ryan <
[EMAIL PROTECTED]> wrote:
We are seeing large numbers of sockets lingering in the CLOSE_WAIT state (waiting for the client to issue a close() call) while running our client application on Linux. The problem does not seem to occur on Windows or Solaris, or at least is not nearly as obvious on Solaris. When the process ends, the sockets are all closed, so it does not appear to be an operating system bug. It does appear that the sockets are eventually closed, but that leads me to believe that they are being left around for the garbage collector to deal with.Does anyone have any insight into this? I read several other peoples messages regarding this, so I am not the only one experiencing this. Is there a way to force the Axis client to call close()? Is this a JVM issue?Thanks for any help.Mike Ryan
