logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Macarron Miegemolle, Eduardo" <e.macar...@iberdrola.es>
Subject RE: log4j JMX implementation
Date Mon, 24 Nov 2003 17:27:55 GMT

	We are not using the Repository Selector method to keep different
instances of log4j for each application, we use the simpler method of
droping log4j.jar on each WEB-INF/lib. So tiding somehow JMX domain to
Repository Selector wont work for us. So I think that JMX domain same should
be configurable as you have already pointed. In fact, the domain name of the
first MBean is provided by application initialitiation code when registers


-----Mensaje original-----
De: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
Enviado el: lunes, 24 de noviembre de 2003 18:00
Para: Log4J Developers List
Asunto: RE: log4j JMX implementation

This is a good point.  We should have the JMX configurable or perhaps tied
to the repository selector, since you will want the log4j repository and JMX
domain to match.

Yoav Shapira
Millennium ChemInformatics

>-----Original Message-----
>From: Macarron Miegemolle, Eduardo [mailto:e.macarron@iberdrola.es]
>Sent: Monday, November 24, 2003 11:55 AM
>To: 'log4j-dev@jakarta.apache.org'
>Subject: log4j JMX implementation
>	Hi There,
>	We are building a light j2ee framework for our company. We are using
>log4j for logging. One important objetive of our framework is to make
>applications manageable, and for that purpose we use JMX.
>	We have planned to use log4j own jmx implementation. Yes, I know its
>already beta, but it has the basic functionallity right now.
> 	I've been reading the code and I have found an issue that could be
>an error. I´m not sure so I need your help.
>	HierarchyDynamicMBean builds other MBeans depending on log4j
>configuration. Those "child" MBeans are created using a domain called
>	This is a problem for us. In our application server we have an
>instance of log4j for each application installed. We plan to use
>own MBeanServer, otherwise admins will have to use different ports to see
>all the MBeans that the server is running.
>	If log4j jmx uses a hardcoded "log4j" string as a domain name we are
>going to have some problems. First: two different log4j instances wont be
>able to register their MBeans as the second log4j instance will recibe an
>exception for trying to register an MBean twice. The other issue is that
>even it it was possible to register them twice, it wont be possible to
>recognize with one corresponds with an application, as all them look the
>	The fastest solution for me is using only one log4j instance for the
>whole server. But this solution introduces some dependendes between
>applications that we´d like to avoid.
>	Any opinion?
>	cheers.
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged.  This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.

To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

View raw message