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 "Mike Calmus (JIRA)" <ji...@apache.org> on 2014/07/28 17:03:39 UTC

[jira] [Created] (LOG4J2-751) JndiContextSelector should skip JNDI lookup when isLog4jContextSelectorNamed is false

Mike Calmus created LOG4J2-751:
----------------------------------

             Summary: JndiContextSelector should skip JNDI lookup when isLog4jContextSelectorNamed is false
                 Key: LOG4J2-751
                 URL: https://issues.apache.org/jira/browse/LOG4J2-751
             Project: Log4j 2
          Issue Type: Improvement
    Affects Versions: 2.0
            Reporter: Mike Calmus
            Priority: Minor


When an app server is configured to use the JndiContextSelector all applications are required to specify log4j/context-name JNDI lookup path or an exception is printed indicating the lookup failed. When the isLog4jContextSelectorNamed parameter is set to false this lookup should not be necessary and should be skipped and no message should be logged,



--
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