Well, I've just checked, and it seems, that I can get the NDC field with chainsaw. But not the MDC. I don't know, why...
The other problem is: only the tomcat, servlets, and bound services get the NDC field (I set it in the servlet Filter), the threads they made don't. So, what should I make if I want all my threads to get the same NDC as servlets? My biggest problem is: I'd like to categorize the logs dependent on which server they arose -- and as far as I know NDC is not for this. It's for collecting information about the Threads the log event went through. Thanks: Bence On 12/5/06, Bence Takács <[EMAIL PROTECTED]> wrote:
Thanks for the tip, it works. I can get the MDC. But I use Chinsaw to view the logs. And Chainsaw can open only an XML-formatted log file. The XmlLayout doesn't use Conversion Patterns -- so I cannot see the MDC on Chainsaw. Is there any solution for this? One solution is obvious: I could subclass the XMLlayout, and change the value of 'logger' attribute from "package.object" into "server.package.object" ... but it seems too complicated for me. Any tips? Thanks: Bence On 12/4/06, Maarten Bosteels <[EMAIL PROTECTED]> wrote: > 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > > >> > > > Sent: maandag 4 december 2006 13:33 > > >> > > > To: [email protected] > > >> > > > 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: [EMAIL PROTECTED] > > >> > > > For additional commands, e-mail: > > >> [EMAIL PROTECTED] > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> --------------------------------------------------------------------- > > >> > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> > > > For additional commands, e-mail: > > >> [EMAIL PROTECTED] > > >> > > > > > >> > > > > > >> > > > > >> > > > > >> --------------------------------------------------------------------- > > >> > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> > > For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > > > >> > > > > >> > > > >> > > > >> > -- > > >> > James Stauffer http://www.geocities.com/stauffer_james/ > > >> > Are you good? Take the test at http://www.livingwaters.com/good/ > > >> > > > >> > --------------------------------------------------------------------- > > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> > For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > > >> > > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
