logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Te L (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4J2-666) Ability to use a custom MBean domain
Date Tue, 08 Jul 2014 22:52:05 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055575#comment-14055575
] 

Te L edited comment on LOG4J2-666 at 7/8/14 10:51 PM:
------------------------------------------------------

"ConfigLocationUri" is an attribute of the log4j2 MBean. It's got a wrong value there.

I am still not sure how to set the context name. Can we provide an easy way to do that perhaps
via the config file?

After using AsyncRoot and AsyncLogger, the MBean name becomes weird:
(with standalone tomcat):
org.apache.logging.log4j2:type="WebappClassLoader\n  context: /hello-world\n  delegate: false\n
 repositories:\n    /WEB-INF/classes/\n----------> Parent Classloader:\norg.apache.catalina.loader.StandardClassLoader@892949f\n"
(with tomcat maven plugin):
org.apache.logging.log4j2:type="WebappClassLoader\n  context: \n  delegate: false\n  repositories:\n---------->
Parent Classloader:\nClassRealm[plugin>org.apache.tomcat.maven:tomcat7-maven-plugin:2.2,
parent: sun.misc.Launcher$AppClassLoader@7d487b8b]\n"

How do I verify the fix? Is there a snapshot build I can download or something?


was (Author: lite2073):
"ConfigLocationUri" is an attribute of the log4j2 MBean. It's got a wrong value there.

I am still not sure how to set the context name. Can we provide an easy way to do that perhaps
via the config file?

After using AsyncRoot and AsyncLogger, the MBean name becomes weird:
(with standalone tomcat):
org.apache.logging.log4j2:type="WebappClassLoader\n  context: /hello-world\n  delegate: false\n
 repositories:\n    /WEB-INF/classes/\n----------> Parent Classloader:\norg.apache.catalina.loader.StandardClassLoader@892949f\n"
(with tomcat maven plugin):
org.apache.logging.log4j2:type="WebappClassLoader\n  context: \n  delegate: false\n  repositories:\n---------->
Parent Classloader:\nClassRealm[plugin>org.apache.tomcat.maven:tomcat7-maven-plugin:2.2,
parent: sun.misc.Launcher$AppClassLoader@7d487b8b]\n"

How do I verify? Is there a snapshot build I can download or something?

> 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
>             Fix For: 2.0
>
>         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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message