JMX and config of log4j in container env.

I recently enabled JMX support for jk, and one of the things it's doing is detect if log4j is available and enable the log4j JMX. There are few problems - and this is a deeper problem, that affects the use of log4j as 'main' logger for tomcat. The first problem is conflicts in the generated nam

DO NOT REPLY [Bug 9738] - Should Hierarchy.resetConfiguration also reset LogLog?

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 9879] New: - Hierarchy constructor is not backward compatible

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: reference to internet for jakarta-logo.gif in html files

I agree. This was discussed some time ago. See http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1553 You may wish to contact the Anakia developers if you feel strongly about this problem. See also http://jakarta.apache.org/velocity/anakia.html At 08:50 14.06.2002 +, you wrote: >Hi, > >some