[
https://issues.apache.org/jira/browse/LOG4J2-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049049#comment-14049049
]
Te L commented on LOG4J2-666:
-----------------------------
I didn't get a chance to work on this until now. Please unzip the attached file
and run "mvn tomcat7:run". The log file is at target/tomcat/logs/service.log.
You can start a jconsole to see the MBeans.
There are two issues here:
- The MBean name is not unique:
org.apache.logging.log4j2:type=AsyncLoggerContext
- ConfigLocationUri attribute points to a wrong location for the log4j2.json
> Ability to use a custom MBean domain
> ------------------------------------
>
> Key: LOG4J2-666
> URL: https://issues.apache.org/jira/browse/LOG4J2-666
> Project: Log4j 2
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 2.0-rc1, 2.0-rc2
> Reporter: Te L
> Assignee: Remko Popma
> Attachments: log4j-mbean-naming.tar.gz
>
>
> I have a few webapps codeployed in the same JVM. I'd like to use log4j 2 for
> all of them but there is a clash in log4j MBeans since they have a fixed
> domain . Could we support customizing the domain for log4j MBeans? I'd like
> to set a different one for each webapp.
> Thanks,
> Te
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
