You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2014/06/12 01:55:02 UTC
[jira] [Commented] (LOG4J2-666) Ability to use a custom MBean
domain
[ https://issues.apache.org/jira/browse/LOG4J2-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028605#comment-14028605 ]
Remko Popma commented on LOG4J2-666:
------------------------------------
I think this was addressed with LOG4J2-500 in release rc1.
Each MBean name contains the logger context name. If you have multiple web apps, their logger context should be unique and therefore the MBean names should not clash.
Which web container are you using? Are you seeing the same LoggerContext name for different web apps?
> 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
> Reporter: Te L
>
> 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