Glad to have ben of some help, and thanks for sharing your results.
It's always fun to deal with an interesting issue and cooperating poster.
As a matter of fact, the result of your investigation will be quite
helpful for me too. Although I'm using mod_jk and not mod_proxy, I'm
quite sure that
Tomcat is back
up.
Ryan Murray
elementn^n
-Original Message-
From: Jenny Brown [mailto:skyw...@gmail.com]
Sent: Wednesday, June 10, 2009 12:43 AM
To: users@httpd.apache.org
Subject: Re: [us...@httpd] 503 status seems to get cached - how do I disable
caching?
Ok, I tried testing
Ryan Murray wrote:
Did you check the timeout on your apache proxy config? Once apache has detected the backend is not available it won't retry again until a certain number of seconds (timeout) has passed. I pretty sure mod_proxy defaults to 60 seconds, which I usually reduce to get a quicker
On Wed, Jun 10, 2009 at 4:06 AM, André Warnier a...@ice-sa.com wrote:
I have not verified, but intuitively I would tend to think that no HTTP
caching mechanism (browser, server, mod_cache, proxies, etc..) would ever
really cache error responses, and keep responding the same from some cache
: Re: [us...@httpd] 503 status seems to get cached - how do I disable
caching?
On Wed, Jun 10, 2009 at 4:06 AM, André Warnier a...@ice-sa.com wrote:
I have not verified, but intuitively I would tend to think that no HTTP
caching mechanism (browser, server, mod_cache, proxies, etc..) would ever
On Wed, Jun 10, 2009 at 8:13 AM, Singh, Sukhjeet
sukhjeet.si...@fiserv.com wrote:
Eric,
I agree with you but as we can fix the custom 404 or 403 errors via
ErrorDocument. Isn't there any way to fix this banner as whenever the 403
Forbidden message is generated it should be replaced with 404
On Wed, Jun 10, 2009 at 3:06 AM, André Warniera...@ice-sa.com wrote:
So, to get back to the original issue : if indeed the observed behaviour
derives from such a timeout on the part of mod_proxy, I would suggest to do
some thinking about whether it is not better, in a general sense, to leave
Jenny Brown wrote:
On Wed, Jun 10, 2009 at 3:06 AM, André Warniera...@ice-sa.com wrote:
So, to get back to the original issue : if indeed the observed behaviour
derives from such a timeout on the part of mod_proxy, I would suggest to do
some thinking about whether it is not better, in a general
You got me going in a good general direction -- the real solution is
slightly different. Here's what I found.
In the parameters section of the ProxyPass directive, there is a
parameter called retry. It defaults to 60 seconds. The description
is such:
Connection pool worker retry timeout in
Regarding the possibility of hung AJP sockets:
That's an interesting question. I have a dev environment where I
could test it out, though it'll be a while before I get an opportunity
to do so. If I can confirm that the absence of pending requests makes
the response time faster, I'll let you
Ok, I tried testing for the hung ajp sockets concept, and got some
other useful info too. Problem still remains.
Procedure:
I stopped all services that make requests to this dev web server (so I
am the only user on).
I stopped both tomcat and apache, and make sure all processes had
exited.
Jenny Brown wrote:
...
Just to get better answers, can you provide some additional information,
such as
- which Apache are you talking about (version) ?
- which Tomcat (version) ?
- how are they connected (connector ?)
- on which platform (OS) ?
Then anyway, as far as I know, /nothing/ is
On Mon, Jun 8, 2009 at 12:10 PM, André Warniera...@ice-sa.com wrote:
Jenny Brown wrote:
...
Just to get better answers, can you provide some additional information,
such as
- which Apache are you talking about (version) ?
Apache/2.2.3 built Nov 12, 2008
- which Tomcat (version) ?
6.0.18
On Mon, Jun 8, 2009 at 12:50 PM, Jenny Brownskyw...@gmail.com wrote:
What you should really try, is to use the browser to access that same URL
directly on Tomcat, without going through Apache, and see how long you have
to wait there to get an answer after you start Tomcat.
Hitting tomcat
Jenny Brown wrote:
On Mon, Jun 8, 2009 at 12:50 PM, Jenny Brownskyw...@gmail.com wrote:
What you should really try, is to use the browser to access that same URL
directly on Tomcat, without going through Apache, and see how long you have
to wait there to get an answer after you start Tomcat.
15 matches
Mail list logo
