You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Glenn Nielsen <gl...@mail.more.net> on 2003/10/22 15:44:54 UTC

Coyote Connector logging

The Coyote docs state the following regarding coyote connector logging:

"Any debugging or exception logging information generated by this Connector will be automatically routed to the Logger 
that is associated with our related Engine. No special configuration is required to enable this support."

But this doesn't seem to work.

The Connector is configured in the Service scope and the Logger is configured in the Engine
scope.  A Service can not have a Logger configured, and an Engine can't have a Connector
configured.

I see logging output from the Coyote Connector going to the default stdout/stderr Tomcat
logs rather than to to the log configured for the Engine.

Am I just mistaken, or is the documented logging behaviour broken?

Regards,

Glenn


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


Re: Coyote Connector logging

Posted by Glenn Nielsen <gl...@mail.more.net>.
Bill Barker wrote:
> ----- Original Message -----
> From: "Glenn Nielsen" <gl...@mail.more.net>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Wednesday, October 22, 2003 11:39 AM
> Subject: Re: Coyote Connector logging
> 
> 
> 
>>
>>Remy Maucherat wrote:
>>
>>>Glenn Nielsen wrote:
>>>
>>>
>>>>The Coyote docs state the following regarding coyote connector logging:
>>>>
>>>>"Any debugging or exception logging information generated by this
>>>>Connector will be automatically routed to the Logger that is
>>>>associated with our related Engine. No special configuration is
>>>>required to enable this support."
>>>>
>>>>But this doesn't seem to work.
>>>>
>>>>The Connector is configured in the Service scope and the Logger is
>>>>configured in the Engine
>>>>scope.  A Service can not have a Logger configured, and an Engine
>>>>can't have a Connector
>>>>configured.
>>>>
>>>>I see logging output from the Coyote Connector going to the default
>>>>stdout/stderr Tomcat
>>>>logs rather than to to the log configured for the Engine.
>>>>
>>>>Am I just mistaken, or is the documented logging behaviour broken?
>>>
>>>
>>>As many components, the connector now logs to commons-logging (with
>>>categories according to its classname), so this particular page in the
>>>docs would need updates :-(
>>
>>Right, I saw that.  So how would you configure Coyote to log to the
>>same log as you configured for the Engine in Tomcat 4.1?
>>
> 
> 
> Change the Engine logging to use c-l? ;-).
> 
> I don't see that it could be done since none of the components outside of
> o.a.c.t5 understand anything about Catalina (and I'm strongly -1 to changing
> this, since it will break 3.3).
> 

And you are right, code outside of o.a.catalina shouldn't need to know anything
about o.a.catalina.

I like the fact that logging is inheritable by nested components in Tomcat 4,
I can't speak for Tomcat 3.3 or 5.0.  The way the latest Coyote Connector
works breaks that contract.  org.apache.coyote.tomcat4.CoyoteConnector uses
org.apache.catalina.Logger yet org.apache.util.net.* uses commons-logging.
That means that you can't log everything related to the same CoyoteConnector
to the same log file,

I don't know what the best solution is, just identified a problem. :-)

Regards,

Glenn








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


Re: Coyote Connector logging

Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Glenn Nielsen" <gl...@mail.more.net>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Wednesday, October 22, 2003 11:39 AM
Subject: Re: Coyote Connector logging


>
>
> Remy Maucherat wrote:
> > Glenn Nielsen wrote:
> >
> >> The Coyote docs state the following regarding coyote connector logging:
> >>
> >> "Any debugging or exception logging information generated by this
> >> Connector will be automatically routed to the Logger that is
> >> associated with our related Engine. No special configuration is
> >> required to enable this support."
> >>
> >> But this doesn't seem to work.
> >>
> >> The Connector is configured in the Service scope and the Logger is
> >> configured in the Engine
> >> scope.  A Service can not have a Logger configured, and an Engine
> >> can't have a Connector
> >> configured.
> >>
> >> I see logging output from the Coyote Connector going to the default
> >> stdout/stderr Tomcat
> >> logs rather than to to the log configured for the Engine.
> >>
> >> Am I just mistaken, or is the documented logging behaviour broken?
> >
> >
> > As many components, the connector now logs to commons-logging (with
> > categories according to its classname), so this particular page in the
> > docs would need updates :-(
>
> Right, I saw that.  So how would you configure Coyote to log to the
> same log as you configured for the Engine in Tomcat 4.1?
>

Change the Engine logging to use c-l? ;-).

I don't see that it could be done since none of the components outside of
o.a.c.t5 understand anything about Catalina (and I'm strongly -1 to changing
this, since it will break 3.3).

> Glenn
>
> ----------------------------------------------------------------------
> Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> MOREnet System Programming               |  * if iz ina coment.      |
> Missouri Research and Education Network  |  */                       |
> ----------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>


Re: Coyote Connector logging

Posted by Glenn Nielsen <gl...@mail.more.net>.

Remy Maucherat wrote:
> Glenn Nielsen wrote:
> 
>> The Coyote docs state the following regarding coyote connector logging:
>>
>> "Any debugging or exception logging information generated by this 
>> Connector will be automatically routed to the Logger that is 
>> associated with our related Engine. No special configuration is 
>> required to enable this support."
>>
>> But this doesn't seem to work.
>>
>> The Connector is configured in the Service scope and the Logger is 
>> configured in the Engine
>> scope.  A Service can not have a Logger configured, and an Engine 
>> can't have a Connector
>> configured.
>>
>> I see logging output from the Coyote Connector going to the default 
>> stdout/stderr Tomcat
>> logs rather than to to the log configured for the Engine.
>>
>> Am I just mistaken, or is the documented logging behaviour broken?
> 
> 
> As many components, the connector now logs to commons-logging (with 
> categories according to its classname), so this particular page in the 
> docs would need updates :-(

Right, I saw that.  So how would you configure Coyote to log to the
same log as you configured for the Engine in Tomcat 4.1?

Glenn

----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------


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


Re: Coyote Connector logging

Posted by Remy Maucherat <re...@apache.org>.
Glenn Nielsen wrote:

> The Coyote docs state the following regarding coyote connector logging:
> 
> "Any debugging or exception logging information generated by this 
> Connector will be automatically routed to the Logger that is associated 
> with our related Engine. No special configuration is required to enable 
> this support."
> 
> But this doesn't seem to work.
> 
> The Connector is configured in the Service scope and the Logger is 
> configured in the Engine
> scope.  A Service can not have a Logger configured, and an Engine can't 
> have a Connector
> configured.
> 
> I see logging output from the Coyote Connector going to the default 
> stdout/stderr Tomcat
> logs rather than to to the log configured for the Engine.
> 
> Am I just mistaken, or is the documented logging behaviour broken?

As many components, the connector now logs to commons-logging (with 
categories according to its classname), so this particular page in the 
docs would need updates :-(

Remy



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