Thank you for your advices.
checking you don't have any server-side profiles configured with an indefinite timeout.
we are using default idletimeout(300sec)
sol10995: TCP connections that do not terminate properly may become zombie connections and cause TMM to leak memory
I checked num of close-wait sessions.
bigpipe tcp show
GLOBAL TCP STATISTICS --
(open, close-wait, fin-wait, time-wait) = (8406, 160456, 250, 732)
:
mmmm... CLOSE-WAIT session seems too many.
Most of our clients are Android devices(smart phones). They may be end up in bad tcp close procedure,
because of weak wave in tunnel, underground,etc...but num of server connection is bigger than client
connection... this point is still unclear and unreasonable for me.
If you know which connection is in CLOSE-WAIT, please tell me.
I would like to know IP address of the peer, will clearify server session or client session.
Anyway, I will also ask to support person too.
Thanks.