[
https://issues.apache.org/jira/browse/LOG4J2-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-666.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0
Fixed in revision 1608149.
MBean names should now be unique for different web applications even when using
{{Log4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector}}.
Please be aware that making all loggers async only works correctly with web
applications if you bundle the log4j2 jar files in WEB-INF/lib in your war
file. (See LOG4J2-493).
Please verify and close.
> 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: [email protected]
For additional commands, e-mail: [email protected]
