At the code location where a particular Thread knows about processing a distinct element you put a identifying information into MDC, after having processed remove the info again. MDC values are kept on a per Thread basis. This info can be used by the MultifileAppender (when processing a log call) or by a own written Repository Selector (when fetching a logger). Heri
> -----Original Message----- > From: Reza Razavipour [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 09, 2008 7:09 PM > To: Log4J Users List > Subject: Re: [SPAM (Bayesain Analysis)] - Logger object and > change filename - Bayesian Filter detected spam > > I have, I just don't see how that works for my case??? > > Reza > > On Tue, Sep 9, 2008 at 9:28 AM, Jacob Kjome <[EMAIL PROTECTED]> wrote: > > Search the list for "MultiFileAppender" or something to the > effect of > > per-thread logging based on MDC values. > > > > Jake > > > > > > On Tue, 9 Sep 2008 09:00:53 -0700 > > "Reza Razavipour" <[EMAIL PROTECTED]> wrote: > >> > >> Ok, let me explain more... > >> > >> I have a set of elements, a queue of them...I have a > thread pool of > >> processors. A processor takes an element from the queue > and logs some > >> information about them. So what I need to do is to log the > >> information about element XYZ to a file called XYZ.log and for > >> element ABC to the file ABC.log and on and on... > >> > >> From the log4j.xml for the app, there is an appender called > >> AllElements, lets say. In addition to all element specific > log files, > >> I need to log to this file also...Now what I need to do is > to "clone". > >> If it is a rollingFileAppender the element specific log appender > >> needs to be the same, the pattern format should be the > same, the only > >> difference is appender file name... > >> > >> So for each element, I need a brand new logger with > appenders exactly > >> the same as the one defined in log4j.xml file, the only > difference is > >> the filename for the appender, there is only one. > >> > >> Does this help at all clarify what I need to do? > >> > >> Thanks > >> Reza > >> > >> > >> > >> > >> On Tue, Sep 9, 2008 at 8:00 AM, Bender Heri > <[EMAIL PROTECTED]> wrote: > >>> > >>> Loggers do not have file names attached. Probably you mean a > >>> FileAppender. > >>> > >>> Each configured Appender is instantiated as singleton, > even if it is > >>> attached to more than one Logger. > >>> > >>> Loggers are identified by a arbitrary String, commonly the FQCN. > >>> Therefore you cant clone a Logger which has the same name as the > >>> original. > >>> > >>> Explain more about your needs. Why do you have to clone it? > >>> > >>> Heri > >>> > >>>> -----Original Message----- > >>>> From: Reza Razavipour [mailto:[EMAIL PROTECTED] > >>>> Sent: Monday, September 08, 2008 5:38 PM > >>>> To: Log4J Users List > >>>> Subject: [SPAM (Bayesain Analysis)] - Logger object and change > >>>> filename - Bayesian Filter detected spam > >>>> > >>>> All, > >>>> > >>>> I have a Logger object and I need to create a "clone" of it and > >>>> change its filename to a different name. How does one do that? > >>>> The idea here is that I have initialized a Logger instance from > >>>> log-4j.xml file. Now I need to create a new one, off of > it or clone > >>>> and change the filename. Every attribute of the new > Logger instance > >>>> should be whatever is in the file, only filename is diifferent. > >>>> > >>>> Thanks in advance. > >>>> Reza > >>>> > >>>> > ------------------------------------------------------------------- > >>>> -- 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] > > > > > > --------------------------------------------------------------------- > 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]
