On 18.02.2016 16:50, Elias, Michael wrote:
Hi -
We are running tomcat version 7.0.50.
Starting 2 days ago are application stopped responding to requests. Our
investigation showed us that we are not closing connections. We see after 300
tcp sessions, for the tomcat PID, in CLOSE_WAIT state out
Hi -
We are running tomcat version 7.0.50.
Starting 2 days ago are application stopped responding to requests. Our
investigation showed us that we are not closing connections. We see after 300
tcp sessions, for the tomcat PID, in CLOSE_WAIT state out app stops responding.
Restarting the app
Hi -
We are running tomcat version 7.0.50.
Starting 2 days ago are application stopped responding to requests. Our
investigation showed us that we are not closing connections. We see after 300
tcp sessions, for the tomcat PID, in CLOSE_WAIT state out app stops responding.
Restarting the app
nect and the port shows a state of established.
>>
>> Any ideas as to why I can no longer reach my web application?
>> Whats causing this close_wait state?
>
> CLOSE_WAIT is when the remote side of a connection closed it.
>
> It seems your proxy tries to reuse an exis
netstat -a shows the port running tomcat
> changes to a state of close_wait.
>
> however, if I telnet to the port (8980) from the server running apache I can
> connect and the port shows a state of established.
>
> Any ideas as to why I can no longer reach my web application?
>
o the port (8980) from the server running apache I can
connect and the port shows a state of established.
Any ideas as to why I can no longer reach my web application?
Whats causing this close_wait state?
thanks,
--
View this message in context:
http://www.nabble.com/tomcat-close_wait-stat
