[
https://issues.apache.org/jira/browse/LOG4J2-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049698#comment-14049698
]
Remko Popma commented on LOG4J2-666:
------------------------------------
... I don't know what you mean by "ConfigLocationUri attribute points to a
wrong location for the log4j2.json".
It looks like your log4j2.json file is located under src/main/resources so I
would expect it gets bundled in your application's jar file and there is no
need to specify a location to tell log4j2 where to find this file...
Also, I could not find "ConfigLocationUri" anywhere in your sample project.
Where are you seeing this? What is the actual value? What is the expected value?
> 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: [email protected]
For additional commands, e-mail: [email protected]
