logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Bosteels" <mbosteels....@gmail.com>
Subject Re: Change the log hierarchy on a log server
Date Mon, 04 Dec 2006 20:39:26 GMT
Instead of subclassing the Tapestry servlet(s) you could implement a
Servlet Filter.
see
http://java.sun.com/products/servlet/Filters.html
and
http://www.rtner.de/software/MDCUserServletFilter.html

On 12/4/06, Takács Bence <takacs.bence@gmail.com> wrote:
> Unfortunately we usually use Tapestry framework, not pure servlet. So in
> that case we would need to override Tapestry's Application Servlet. Is
> there any other way to do this?
>
> What about the appenders? Or can I somehow override the root logger to
> do the thing?
>
> Thanks:
>    Bence
>
>
> James Stauffer wrote:
> > AFAIK there is no way to set it in the config file so one way to set
> > it is to call MDC.put("server", serverName) at the beginning of every
> > doGet or doPost.  Another option may be to have the socket server call
> > MDC.put("server", clientName) but I haven't tried that option.
> >
> > On 12/4/06, Bence Takács <takacs.bence@gmail.com> wrote:
> >> Hello
> >>
> >> I'm sorry, I haven't used MDC before. How can I set it from the config
> >> (properties, or xml) file?
> >>
> >> What do you mean "at the beginning of every servlet call"? You mean
> >> that all my servlet has to set MDC in the doGet(), and doPost()
> >> methods? Could you write an example code?
> >>
> >> Thanks:
> >>    Bence
> >>
> >> On 12/4/06, James Stauffer <stauffer.james@gmail.com> wrote:
> >> > If you set the MDC at the beginning of every servlet call then most
> >> > errors will have it set.
> >> >
> >> > On 12/4/06, Bence Takács <takacs.bence@gmail.com> wrote:
> >> > > Hello
> >> > >
> >> > > Could you express, what do you mean? In the documentation there
> >> is no
> >> > > example for managing MDC-s from config files (only for reading
> >> them).
> >> > > But I cannot change tomcat's codes, i can change it's logging
> >> > > properties from the logging.properties, or xml file.
> >> > >
> >> > > Could you help me, how can I manage MDC through this kinds of
> >> config files?
> >> > >
> >> > > Thanks:
> >> > >    Bence
> >> > >
> >> > >
> >> > > On 12/4/06, Blok, Eelke <eelke.blok@numico.com> wrote:
> >> > > > I don't have experience with Log4J in Tomcat, but the usual
> >> solution is to make sure the originating server is in an MDC field.
> >> This may well be taken care of in your setup already.
> >> > > >
> >> > > > -----Original Message-----
> >> > > > From: Bence Takács [mailto:takacs.bence@gmail.com]
> >> > > > Sent: maandag 4 december 2006 13:33
> >> > > > To: log4j-user@logging.apache.org
> >> > > > Subject: Change the log hierarchy on a log server
> >> > > >
> >> > > >
> >> > > > Hello
> >> > > >
> >> > > > I have a log server (SimpleSocketServer), which gathers all the
> >> log4j clients log. All the clients use their application specific
> >> settings, and a root logger (in ERROR level) to catch tomcat Exceptions.
> >> > > >
> >> > > > To the server the log hierarchy is like this:
> >> mycountry.mycompany.myapplication1
> >> > > > mycountry.mycompany.myapplication2
> >> > > > mycountry.mycompany.myapplication3
> >> > > > org.apache.catalina
> >> > > >
> >> > > > In this way if I get a tomcat error, I don't know which server
> >> was the source of the exception.
> >> > > >
> >> > > > Does any way to change the logging hierarchy like this:
> >> myserver1.mycountry.mycompany.myapplication1
> >> > > > myserver1.org.apache.catalina
> >> myserver2.mycountry.mycompany.myapplication2
> >> > > > myserver2.org.apache.catalina
> >> myserver3.mycountry.mycompany.myapplication3
> >> > > > myserver3.org.apache.catalina
> >> > > >
> >> > > > Thanks:
> >> > > >   Bence
> >> > > >
> >> > > >
> >> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >> > > > For additional commands, e-mail:
> >> log4j-user-help@logging.apache.org
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >> > > > For additional commands, e-mail:
> >> log4j-user-help@logging.apache.org
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >> > > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >> > >
> >> > >
> >> >
> >> >
> >> > --
> >> > James Stauffer        http://www.geocities.com/stauffer_james/
> >> > Are you good? Take the test at http://www.livingwaters.com/good/
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >> > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >>
> >>
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
Mime
View raw message