I am observing what I consider a log4j problem, but cannot find any mention of this behavior in any doc or web/newsgroup/mail archive.
My log4j initializes just fine. I have my root Category defined in my log4j.properties to WARN. I then programmatically get an a handle to my root Category instance, and set its priority to DEBUG. I then cause another class (not specified to any logging in log4j.props, so it always assumes root Category's priority) to initialize it's log4j category, and would expect it to inherit the newly modified priority on the root, but instead its priority is that of the root definition in the log4j.properties file -- it seems that the log4j.properties definition of priority takes precedence over the in-memory instance. This does not make sense to me. Seems the instantiated category (at any level in the hierarchy, not just root) should take precedence over the log4j.properties. I do not want to modify my log4j.properties file on the fly -- this is for temporary debugging. Btw, we're using Log4j 1.0.4, thus working with Category still... TIA! Brian __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
