Removing TCP sockets left open

["BURN, James" <Ja...@oup.com>]

Hi

We're running ServiceMix 5.1.1 on Redhat and have tcp Sockets being left open when our transport route fails through overloading.

We're putting some throttling into place to try and avoid the failure problems, but I'm still puzzled why we're getting file descriptors for open TCP sockets when there are (according to my Java monitoring) not the same number of threads (live or finished) with these open sockets.

I'm checking the open transport connections with:

ss -pat '( dst :443 or dst :80 )'

and am getting hundreds of connections listed as:

ESTAB      0      0         ::ffff:<SM IP ADDRESS>:34702    ::ffff:<OUTBOUND IP ADDRESS>:https    users:(("java",10956,2082))

In this line, 10956 is the pid running ServiceMix, and 2082 the filedescriptor of the open socket.

Is there anyway of freeing up these old connections without restarting ServiceMix? Or controlling a maximum number of open sockets through ServiceMix?

Thanks

James




Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.