Hello I'd like to avoid using an alpha. So, I will wait for the release. Until then I have to solve the problem with the current version.
I don't know how can I configure the SimpleSocketServer to get the ip and put it somewhere in the log file. This would be the best solution for my problem. There is not so much about the SimpleSocketServer in the documentation (I have the version 1.2.9). Do you have any further information about it? Thanks: Bence On 12/4/06, Scott Deboy <[EMAIL PROTECTED]> wrote:
Look at PropertyFilter in log4j 1.3 alpha for an example of how you can have arbitrary static properties added to events. Also, SimplesocketServer has the ip address of the sending socketappender - you could try to use that. Scott Deboy Principal Engineer COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Telephone: 503.224.7496 Cell: 503.997.1367 Fax: 503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -----Original Message----- From: James Stauffer [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 9:20 AM To: Log4J Users List Subject: Re: Change the log hierarchy on a log server 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] > > -- 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]
