Thank you Bill!
I will happily continue to the other list, at least I know my logging is
set to capture the correct events and I have a clue as to what might be
the cause.
-Collin
Bill Barker wrote:
"Collin McClendon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
I've enabl
"Collin McClendon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I've enabled the logging per your suggestions, and not having heard back
> in a bit, I was hoping someone could clue in to why I get plenty of FINE
> messages for org.apache.jk.common.MsgAjp, but no longer get SE
I've enabled the logging per your suggestions, and not having heard back
in a bit, I was hoping someone could clue in to why I get plenty of FINE
messages for org.apache.jk.common.MsgAjp, but no longer get SEVERE
messages. I'm also trying consistently crash mod_jk, but not having
much luck,
Bill,
so far all I've gotten out of FINE logging is a lot of these:
Jul 14, 2005 1:44:36 PM org.apache.jk.common.MsgAjp processHeader
FINE: Received 560 18
We have been monitoring the server, and even though I got no SEVERE
messages, it appears to have hung as before. Am I excluding SEVERE
log
Wednesday, July 13, 2005 8:15 AM
Subject: Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow (logging)
Bill,
Thanks again for this tip. After reading the document to my best
ability, I added this line to the end of
/usr/local/tomcat/common/classes/logging.propeties :
org.apache.jk.common.MsgAjp =
That's for log4j. For Juli, you want FINE (or FINEST).
- Original Message -
From: "Collin McClendon" <[EMAIL PROTECTED]>
To: "Tomcat Developers List"
Sent: Wednesday, July 13, 2005 8:15 AM
Subject: Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow (lo
List"
Sent: Tuesday, July 12, 2005 10:57 AM
Subject: Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow
Thanks so much for replying! I can understand that concept. Given that
we are using mod_jk to connect the Apache frontend to Tomcat running
OpenCMS on the backend, perhaps the way that the a
Thanks,
I'll read up on this.
Bill Barker wrote:
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html
- Original Message -
From: "Collin McClendon" <[EMAIL PROTECTED]>
To: "Tomcat Developers List"
Sent: Tuesday, July 12, 2005 10:57 AM
Subjec
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html
- Original Message -
From: "Collin McClendon" <[EMAIL PROTECTED]>
To: "Tomcat Developers List"
Sent: Tuesday, July 12, 2005 10:57 AM
Subject: Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow
Than
Thanks so much for replying! I can understand that concept. Given that
we are using mod_jk to connect the Apache frontend to Tomcat running
OpenCMS on the backend, perhaps the way that the application is working
that is giving us this result? Also in response to Bill, where can one
turn on
DE
Bill Barker wrote:
The message is simply that you have a header value that is too big for the
AJP/1.3 protocol to handle. If you enable DEBUG logging for
org.apache.jk.common.MsgAjp, you should get a dump of the partial data that
should include the name of the bad header.
Given the line, it co
ollin McClendon" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, July 12, 2005 9:38 AM
Subject: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow
> Hello all,
> I was kindly redirected to this list by Mr. Turk, the author of mod_jk.
> He suggested that someone here might be able to d
Hello all,
I was kindly redirected to this list by Mr. Turk, the author of mod_jk.
He suggested that someone here might be able to determine
why when using mod_jk and tomcat and apache, I am getting buffer
overflow messages in the catalina.out logfile. This tends to
happen after 8 hours or so,
13 matches
Mail list logo