A TCP connection goes to state TIME_WAIT after the local end has been
closed in an orderly way (that is not with a connection reset). On a
system that opens and closes many connections, it is therefore normal
to see many connections in this state. This is not a problem, since in
this state, no resources (other than the corresponding entries in some
internal OS data structure and that you can see with netstat) are
consumed whatsoever.
I don't know the exact effect of setCallTransportCleanup(true), but it
may potentially produce even more connections in state TIME_WAIT
because connections are not reused.
Andreas
On 09 Feb 2008, at 10:41, Michele Mazzucco wrote:
On 8 Feb 2008, at 23:57, h b wrote:
Hello, I'm using a stub that is connecting the server using TCP
transport. I'm looping around calling the service operation.
After I'm done I run netstat -na and I see a whole lot of
connections in TIME_WAIT. Can I instruct the stub to clean up the
connection after a method call?
Try options.setCallTransportCleanup(true)
Michele
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
