RE: Log4j Domains

[Scott Deboy]

Title: Message

I can't really answer your question on domains, but I have something that will help you not have to munge the loggers:  Chainsaw v2.   It makes examining information such as a userid in the MDC much simpler (for example, you can tell Chainsaw to send events for each unique mdc.userid to it's own tab), and the _expression_ language used to define colors and which events are on the screen supports mdc lookups.   For example, to only see a single person's events, specify this _expression_ in the 'focus on' text field: MDC.userid == 2222   To make each unique MDC.userid show up on it's own tab, open the 'application-wide preference panel and enter this into the 'tab identifier' field: MDC.userid   Let me know if you're interested in trying it or have questions.  Paul Smith posted a chainsaw install ant script that will download the cvs tip and get everything set up with a single command from the console.   Scott -----Original Message----- From: Bruce Deen [mailto:[EMAIL PROTECTED] Sent: Friday, December 12, 2003 9:57 AM To: [EMAIL PROTECTED] Subject: Log4j Domains I have a question about Log4J Domains, I noticed this is on the planning page for Log4J 1.3.  Will the Log4J Domain allow change to what is currently conceived as a Category?   My current issue is that I have a JRun 4 application server, on this server I have multiple web applications with multiple users who, although not intentionally, sometimes have multiple sessions.  I’m trying to make my logging be based off of each person (if it is a web request) and then a sub-category of their session id.  The way I do this is using Filters, MDC to store user identification and session identification and then use a static getLogger(String n) method that will query the MDC for the extra personalized information and append this onto the start of the category.  Once I do this I can use LogFactor5 and simply turn off the noise of everyone else’s logging for their sessions and focus in on the person who reports a problem or that I notice exceptions for and track a clearer picture of the steps taken to create the exception. Especially if I have 100 simultaneous users on one server.   So will Log4J Domains help me solve my problem without resorting to calling a static method to acquire the Logger each and every time I wish to log something in a method?