Hellow,
I have two Aix 5.2 boxes. The first one run websphere 5.02 and the
second one runs Oarcle 10. I know I have a bug in the application
running on the websphere side. Due to this bug sockets are not closed
an stay forever in close_wait situation. The socket can be seen only
from the webspher side. I have waited for some hourse
but the are stiil open
tcp4 0 0 WebsphereHost.33441 OracleHost.1521 CLOSE_WAIT
tcp4 0 0 WebsphereHost.33443 OracleHost.1521 CLOSE_WAIT
tcp4 0 0 WebsphereHost.33445 OracleHost.1521 CLOSE_WAIT

I know it is possible to say to which procees on the WebSphere
Side those processes belong to (lsof -i) but I dont want to kill this
Java process. My question is how to "kill" those sockets
or force them to disappear during the weakend....

TIA
Uri

mtfuri@fibimail.co.il wrote in news:1121433209.079175.320690
@g49g2000cwa.googlegroups.com:

> Hellow,
> I have two Aix 5.2 boxes. The first one run websphere 5.02 and the
> second one runs Oarcle 10. I know I have a bug in the application
> running on the websphere side. Due to this bug sockets are not closed
> an stay forever in close_wait situation. The socket can be seen only
> from the webspher side. I have waited for some hourse
> but the are stiil open
> tcp4 0 0 WebsphereHost.33441 OracleHost.1521 CLOSE_WAIT
> tcp4 0 0 WebsphereHost.33443 OracleHost.1521 CLOSE_WAIT
> tcp4 0 0 WebsphereHost.33445 OracleHost.1521 CLOSE_WAIT
>
> I know it is possible to say to which procees on the WebSphere
> Side those processes belong to (lsof -i) but I dont want to kill this
> Java process. My question is how to "kill" those sockets
> or force them to disappear during the weakend....

You cannot kill them, they are not processes but connections that the
kernel's TCP stack is aware of.

man no (network options command), relevant options are tcp_timewait,
tcp_keepidle and tcp_keepint.

You should look at changing the TCP_TIMEWAIT variable, I refer you to
http://publib.boulder.ibm.com/infoce...6r0/index.jsp?
topic=/com.ibm.websphere.base.doc/info/aes/ae/tprf_tuneaix.html.

no -o tcp_timewait = 1 # 15 seconds


0xbeef

mtfuri@fibimail.co.il wrote:
> Hellow,
> I have two Aix 5.2 boxes. The first one run websphere 5.02 and the
> second one runs Oarcle 10. I know I have a bug in the application
> running on the websphere side. Due to this bug sockets are not closed
> an stay forever in close_wait situation. The socket can be seen only
> from the webspher side. I have waited for some hourse
> but the are stiil open
> tcp4 0 0 WebsphereHost.33441 OracleHost.1521 CLOSE_WAIT
> tcp4 0 0 WebsphereHost.33443 OracleHost.1521 CLOSE_WAIT
> tcp4 0 0 WebsphereHost.33445 OracleHost.1521 CLOSE_WAIT
>
> I know it is possible to say to which procees on the WebSphere
> Side those processes belong to (lsof -i) but I dont want to kill this
> Java process. My question is how to "kill" those sockets
> or force them to disappear during the weakend....

Did you try rmsock? In some cases it worked for me. Still
this is not a good solution. Get your App. fixed as soon
as possible!

Regards,

Frank