I would like to have a filter invoked when ever a request comes in that does
not represent a valid page/url (404's). What we are doing now is mapping the
error-code to a jsp page that redirects via
(see code below) but of course that is another round trip and therefore not
optimal.
Code:
ro
Martin Gainty wrote:
>
> your diagnostic appears out of sync with your source. where did you
> acquire the source?
>
The app is deployed under the the binary distribution gotten from the web
site (http://tomcat.apache.org/download-55.cgi). We do not compile from the
source, at least not yet. I
Nelson, Tracy wrote:
> Why not just grab the source
I looked at the source (org.apache.tomcat.util.threads.ThreadPool) and it IS
logging to the commons logger - see below.
private static void logFull(Log loghelper, int currentThreadCount,
int maxThreads) {
I need to be notified when ever a Tomcat v5.5 server is over the threadpool
limit. I am already monitoring log4j log messages but the logFull message
appears to me to be a System.out log, by-passing log4j (catalina.out text
shown below).
Nov 17, 2006 12:08:25 PM org.apache.tomcat.util.threads.Thr
