Dear All,we developed and deployed a service based on the java-ws-core-4.0.4. After some running time I noticed that the container process leaves many open connections in the CLOSE_WAIT state. I suspect this is the cause of the stalling of the service that periodically occurs. Restarting the container solves the problem just for a short time.
Googling for this problem I discovered this page: http://www.sunmanagers.org/pipermail/summaries/2006-January/007068.html that seems to explain what is the cause of the opened connections.Can I access sockets of invoked services from my service code? In this case I could check if, after the invocation, they are properly closed... but I don't think this is possible because there is axis under service stubs.
Any better idea? Is this a known problem? Here is some (maybe useful) information to understand what happens:-O.S.: Scientific Linux 3.0, the limit of open files for the user running the container is set to 1024. -Container: java-ws-core-4.0.4 started with -nosec option as a non-root user. -Service: created following the MathService tutorial approach, protected with GSISecureConversation.
Thanks in advance. Cheers, Paolo Roccetti
smime.p7s
Description: S/MIME cryptographic signature
