Remko Popma created LOG4J2-1171:
-----------------------------------
Summary: LoggerContext names are cryptic
Key: LOG4J2-1171
URL: https://issues.apache.org/jira/browse/LOG4J2-1171
Project: Log4j 2
Issue Type: Improvement
Components: Configurators, JMX
Affects Versions: 2.4.1, 2.4, 2.3
Reporter: Remko Popma
Priority: Minor
LoggerContext names currently look like "5e90b76c", or "AsyncContext@5e90b76c".
Originally the LoggerContext name was ClassLoader.toString(), but this had
issues for very long multi-line classloader descriptions (LOG4J2-666).
The problem with the current naming is that a web container with multiple web
applications deployed will not be able to map the JMX MBean to the correct web
application. Similarly, debug-level status messages at startup cannot be mapped
to the correct web app.
The place to address this is probably {{Log4jContextFactory.getContext(String
fqcn, ClassLoader loader, Object externalContext, boolean currentContext, URI
configLocation, String name)}}. The specified name is essentially ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
