, December 27, 2011 10:58:29 PM
Subject: Re: Tomcat HTTPS Connector Stops working after an hour
On 27/12/2011 10:47, Saravanan L wrote:
3. A 504 response code is a gateway timeout. Tomcat does not issue
this
on its own. Either you have a proxy in front of Tomcat or your
application is returning
threads to me.
In comet idle threads are fine rights. Thats how comet/nio works right. Please
correct me on this.
On 12/27/2011 4:03 PM, Mark Thomas wrote:
On 27/12/2011 08:55, Saravanan L wrote:
Tried netstat. 443 is listening, but I cannot connect to it.
I assume it shows no open
Tried netstat. 443 is listening, but I cannot connect to it.
Secondly Thread dump - I could not find any signs of problem or anything
relative to the current issue in the threaddump [Please find the
threaddump in my previous post].
On 12/27/2011 2:11 PM, ma...@apache.org wrote:
Saravanan
users@tomcat.apache.org
Sent: Tuesday, December 27, 2011 10:58:29 PM
Subject: Re: Tomcat HTTPS Connector Stops working after an hour
On 27/12/2011 10:47, Saravanan L wrote:
3. A 504 response code is a gateway timeout. Tomcat does not issue this
on its own. Either you have a proxy in front of Tomcat
:
Saravanan,
On 12/23/11 7:03 AM, Saravanan L wrote:
Please find the latest thread dump attached with mail.
Tomcat 7 still crashes without acceptCount. I am wrong on this
assumption.
The response code is 504. It takes about 2 hours for this occur.
The last status in http-apr-443 (In Server status
,
0x7fc5bb17, 0x7fc5bc6f)
object space 64000K, 74% used
[0x7fc5b72f,0x7fc5ba19d448,0x7fc5bb17)
---DUMP END-
On 12/22/2011 6:45 PM, Caldarale, Charles R wrote:
From: Saravanan L [mailto:saravan...@te-soft.com]
Subject: Fwd: Tomcat
Hi,
We have setup Tomcat 7 with APR in linux box. The issue is that after an
hour or two, the https stops responding, but the HTTP connector is still
working.
When we try to open https://192.168.1.32/, it does not respond.[ it does
not timeout but the browser says server could not reached]
