One solution that I suggest is, store all 5 logger instances in hashtable, store this hashtable into session and every process that wants to log information will first retreive the handle to the logger instance by passing some unique parameter. The disadvantage of this method is that for every log: 1. You need to have seperate configuration parameters... 2. One logger instance will serve purpose of writing either debug, fatal, or any other log type.
But the reason why its writing to all logger is because you have not created seperate instances of logger... Manoj Rathod Patni Computers System. Work *: (434) 845 0911 Ext: 4101 Home *: (434) 385 4113 -----Original Message----- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 6:58 PM To: Log4J Users List Subject: RE: Wrapper Classes - duplication of log statements sounds like your creating a new configuration instead of using your singleton. its happened to me. [DOH!!!] James Mitchell > -----Original Message----- > From: Anand M S [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 29, 2002 2:36 PM > To: Log4J Users List > Subject: Wrapper Classes - duplication of log statements > > > > Hi, > I have 5 loggers (Debug, error, all, info, warning), Im using > my own wrapper classes to use log 4j, when I try to write to log > file (separately for each logger), its writing to all loggers > and duplicating the log statements > > Here is the example, > > > > DebugLogger.log(priority, Log statement), then it writes this > log statement to DebugLogger more than once and to other loggers as well > > > > Am I missing any thing, please help me. > > > > Thanks, > > Anand > > > > > > --------------------------------- > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
