You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Mike Dillon <md...@citysearch.com> on 2003/10/14 01:10:42 UTC

Log4j debugging of Coyote HTTP/1.1 connector

Hello-

I am trying to debug an OutOfMemoryError that I think is occuring inside
of the Coyote connector. I have tried a couple of approaches to try to
get logging, but I can't get a stack trace for these errors.

    1. I stuck a log4j.properties file in common/classes/ setting the
       level for the "org.apache.coyote" category to DEBUG (with a
       stdout appender). This caused a few messages from Http11Protocol
       to end up in my catalina.out, but I saw none of the debug
       messages in org.apache.coyote.tomcat4.OutputBuffer.

    2. I stuck a log4j.properties file in the WEB-INF/classes of my
       webapps/axis directory. This had no effect on the
       org.apache.coyote log statements for the container, as I
       expected.

Can someone please tell me what I need to do to get the log messages in
org.apache.coyote.tomcat4.OutputBuffer to show up in my catalina.out
file?

-md

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

Re: Log4j debugging of Coyote HTTP/1.1 connector

Posted by Mike Dillon <md...@citysearch.com>.
On Mon, Oct 13, 2003 at 11:07:32PM -0700, Bill Barker wrote:
> Should work fine as long as your log4j jar file is in common/lib.
> This is my usual configuration for debugging Tomcat problems.

Actually, I was simply wrong to think that these messages were going
through commons-logging or log4j. When I further examined the "log"
method, I found that is was simply using System.out.println and that it
was only controlled by a compiled-in constant.

Sorry to waste your time.

-md

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

Re: Log4j debugging of Coyote HTTP/1.1 connector

Posted by Bill Barker <wb...@wilshire.com>.
"Mike Dillon" <md...@citysearch.com> wrote in message
news:20031013231042.GA18849@jebus.cs.tmcs...
> Hello-
>
> I am trying to debug an OutOfMemoryError that I think is occuring inside
> of the Coyote connector. I have tried a couple of approaches to try to
> get logging, but I can't get a stack trace for these errors.
>
>     1. I stuck a log4j.properties file in common/classes/ setting the
>        level for the "org.apache.coyote" category to DEBUG (with a
>        stdout appender). This caused a few messages from Http11Protocol
>        to end up in my catalina.out, but I saw none of the debug
>        messages in org.apache.coyote.tomcat4.OutputBuffer.
>

Should work fine as long as your log4j jar file is in common/lib.  This is
my usual configuration for debugging Tomcat problems.

>     2. I stuck a log4j.properties file in the WEB-INF/classes of my
>        webapps/axis directory. This had no effect on the
>        org.apache.coyote log statements for the container, as I
>        expected.
>
> Can someone please tell me what I need to do to get the log messages in
> org.apache.coyote.tomcat4.OutputBuffer to show up in my catalina.out
> file?
>
> -md




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