The implementation should be based on OpenJMX rather than Sun RI. Sun's implementation of JMX is really buggy and OpenJMX offers nices features. Have a look at http://openjmx.sourceforge.net.
Jerome. ----- Original Message ----- From: "Ceki Gülcü" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 21, 2002 6:57 AM Subject: JMX support, call for volunteer(s). > > Hi all, > > As you might know, log4j 1.2 adds JMX support. This JMX code is not > finished but shows promise. I really had fun coding this. However, I > now would like to offer someone else an opportunity to continue the > work. If you have a week or two to spare, and are looking for a nice > little but still high-impact project, look no further. > > Let me know if you are interested. Regards, Ceki > > ps: If you would like to play around with existing JMX support, read > the attached note below. > > >Delivered-To: [EMAIL PROTECTED] > >Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm > >List-Unsubscribe: <mailto:[EMAIL PROTECTED]> > >List-Subscribe: <mailto:[EMAIL PROTECTED]> > >List-Help: <mailto:[EMAIL PROTECTED]> > >List-Post: <mailto:[EMAIL PROTECTED]> > >List-Id: "Log4J Users List" <log4j-user.jakarta.apache.org> > >Reply-To: "Log4J Users List" <[EMAIL PROTECTED]> > >Delivered-To: mailing list [EMAIL PROTECTED] > >X-Sender: [EMAIL PROTECTED] > >X-Mailer: QUALCOMM Windows Eudora Version 5.1 > >Date: Thu, 21 Feb 2002 06:33:46 +0100 > >To: "Log4J Users List" <[EMAIL PROTECTED]> > >From: Ceki Gülcü <[EMAIL PROTECTED]> > >Subject: Re: JMX support in 1.2beta3 > >X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > > >Charlie, > > > >The following is messy, but just to give you an idea of the flavor of > >the beast. > > > >1) Put /java/jmx/lib/jmxri.jar > > /java/jmx/lib/jmxtools.jar > > /jakarta-log4j-1.2beta3/src/java > > /jakarta-log4j-1.2beta3/dist/classes > > > >into your classpath, changing directory names according to your > >environment. > > > >2) cd /jakarta-log4j-1.2beta3/src/java/org/apache/log4j/jmx > > > >3) javac T.java > > > >Do not skip step 3 even if the file T.class is already in the distrib. > > > >4) java T > > > >You'll see output similar to > >0 INFO [main] org.apache.log4j.jmx.Agent - Registering HtmlAdaptorServer > >instance. > >0 INFO [main] org.apache.log4j.jmx.Agent - Registering > >HierarchyDynamicMBean instance. > >10 DEBUG [main] org.apache.log4j.jmx.HierarchyDynamicMBean - preRegister > >called. Server=com.sun.management.jmx.MBeanServerImpl@67e > >89, name=log4j:hiearchy=default > >10 DEBUG [main] org.apache.log4j.jmx.HierarchyDynamicMBean - postRegister > >is called. > >20 DEBUG [main] root - preRegister called. > >Server=com.sun.management.jmx.MBeanServerImpl@67e89, name=log4j:logger=root > >20 DEBUG [main] org.apache.log4j.jmx.LoggerDynamicMBean - Adding > >AppenderMBean for appender named console > >40 DEBUG [main] org.apache.log4j.jmx.AppenderDynamicMBean - preRegister > >called. Server=com.sun.management.jmx.MBeanServerImpl@67e8 > >9, name=log4j:appender=console > >40 DEBUG [main] org.apache.log4j.jmx.AppenderDynamicMBean - Adding > >LayoutMBean:console,layout=org.apache.log4j.PatternLayout > >50 DEBUG [main] org.apache.log4j.jmx.LayoutDynamicMBean - preRegister > >called. Server=com.sun.management.jmx.MBeanServerImpl@67e89, > > name=log4j:appender=console,layout=org.apache.log4j.PatternLayout > >50 DEBUG [main] org.apache.log4j.jmx.LayoutDynamicMBean - getMBeanInfo called. > >50 DEBUG [main] org.apache.log4j.jmx.AppenderDynamicMBean - getMBeanInfo > >called. > >50 DEBUG [main] org.apache.log4j.jmx.HierarchyDynamicMBean - ---Adding > >logger [root] as listener. > > > > > >5) View http://localhost:8082/ with your browser. Do not stop or kill > >"java T". > > > >6) Play around. You can add new appenders to categories, view and > >configure appenders, add layouts... > > > >JMX support is not production quality but the ideas are there. The > >existing code needs polishing... > >Any volunteers? Regards, Ceki > > > >At 16:57 20.02.2002 -0800, Charlie Cano wrote: > > > >>I have to say that the idea of JMX support for the logging service of > >>Log4J is very exciting - is there any current documentation about what > >>the general layout of MBeans are and how they should be used to > >>configure/access the log4j system? I'm poking around the 1.2 API docs, > >>but it's a little tricky to figure out the intention of each MBean in > >>terms of controlling the log4j backend... > >> > >>Thanks, > >>Charlie > > > -- > 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]>
