Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 36385]  -
    [mod_jk1.2.14] Prepost pings are not sent before the first request
Message-Id: <20050902145338.0A7B7122@ajax.apache.org>
Date: Fri,  2 Sep 2005 16:53:38 +0200 (CEST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36385>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36385


------- Additional Comments From remm@apache.org  2005-09-02 16:53 -------
(In reply to comment #9)
> at least you could be sure some sort of code in the request handler is still
> alive and running.

Yes, it means the acceptor thread has managed to allocate a processor thread. If
it can't it's supposed to close the socket, though, which should indicate the
Tomcat instance is "down".

If it does allocate the processor and starts doing things, I don't see how it
can fail to send a pong back. What is the Tomcat state where there would be a
problem ?

(BTW, I think I've fixed the biggest AJP APR bugs, so you can test it: if your
servers have resource efficiency issues, then it can't hurt)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org