kers in
an error state with no timeout."
I changed it to 0 on my dev server, retested, and it works
beautifully. Once I bring Tomcat back up, Apache recovers right away.
This is the behavior I wanted.
Thanks for the help! Problem solved.
Jenny Brown
On Wed, Jun 10, 2009 at 2:31 PM
would I go about
finding out / where should I look?
Jenny Brown
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-u
s a
header it's setting in the response that affects results? I'm still
puzzled. Thanks.
Jenny Brown
On Tue, Jun 9, 2009 at 3:37 PM, Jenny Brown wrote:
> Regarding the possibility of hung AJP sockets:
>
> That's an interesting question. I have a dev environment where I
#x27;ll let you know. Likewise if that's not
the issue, I'm back to the drawing board on it.
Thanks for the ideas.
Jenny Brown
On Mon, Jun 8, 2009 at 1:13 PM, André Warnier wrote:
> Jenny Brown wrote:
>>
>> On Mon, Jun 8, 2009 at 12:50 PM, Jenny Brown wrote:
>>>
On Mon, Jun 8, 2009 at 12:50 PM, Jenny Brown 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.
>
> Hi
On Mon, Jun 8, 2009 at 12:10 PM, André Warnier 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)
f caching? I'd like to not have to wait for the httpd cache to
expire before I can reach the tomcat manager page - especially on
systems with other users where I can't just avoid hitting the page
while it's down. If any user hits it,
