*Point 1 and 2. *
1. When I remove acceptCount=10000 My tomcat 7 works fine.
2. But I had the same property in tomcat 6 and it worked fine on that.
A. I tried remove and altering some variables to check this problem.
Mistakenly I thought acceptCount was the culprit, because
after removing acceptCount, tomcat was running for 2 hours then 443
connector stopped. Tomcat 6 with the same configuration (server.xml)
works fine.
*Point 4*
4. Also found out that when it reaches 9000 connections with my existing
connector [See below] the tomcat https [Http works fine] stops
responding and the browser says 'Connection reset by peer'.
A. When the request count reaches 9000, the tomcat fails within minutes.
This depends , the last two times I tested, I was able to reproduce this.
Log from Tomcat Server status.
(after 1/half hour)
Max threads: 5000 Current thread count: 209 Current thread busy: 2
Keeped alive sockets count: 56
Max processing time: 300477 ms Processing time: 8788.765 s Request
count: 9926 Error count: 783 Bytes received: 0.22 MB Bytes sent: 5.43 MB
On 12/28/2011 2:37 PM, ma...@apache.org wrote:
Saravanan L<saravan...@te-soft.com> wrote:
Tomcat does not pass through any proxy. My firefox browser has a proxy
plugin configured which RELAYED this message.
I enabled this plugin because, I wanted to be sure of whats happening.
(I guess I should made it clear)
So the end line is tomcat does not responds to the request at all.
Firefox says- Connection reset by peer.
Chrome says - Same as above but in a different manner
Firefox with Proxy - 504
Q. how your system is configured
A. Just tomcat running in linux box (Fedora) with APR and Native
compiled.
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 this value.
A. Yes the proxy relayed this message, it seems the tomcat did not
respond with any message at all.
----- Original Message -----
From: "Mark Thomas"<ma...@apache.org>
To: "Tomcat Users List"<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 or your
application is returning this value.
A. Yes the proxy relayed this message, it seems the tomcat did not
respond with any message at all.
Which is the first mention in this thread that you are accessing Tomcat
via a proxy which makes most of the previous contents of this thread
null and void.
I think you need to start again with a more complete description of how
your system is configured. This is look less and less like a Tomcat
issue and more and more like a poorly configured proxy.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Ok. So go back a few messages and address points 1, 2 and 4.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
--
Regards
*Saravanan.L*
This message and any attachment(s) contained here are information that is
confidential, proprietary to TE Software Services and its customers. Contents
may be privileged or otherwise protected by law. The information is solely
intended for the individual or the entity it is addressed to. If you are not
the intended recipient of this message, you are not authorized to read,
forward, print, retain, copy or disseminate this message or any part of it. If
you have received this e-mail in error, please notify the sender immediately by
return e-mail and delete it from your computer.
