Thomas Papke created LOG4J2-1327:
------------------------------------

             Summary: JMX setting for ConfigLocationUri are rewriten after 
change to a invalid Path
                 Key: LOG4J2-1327
                 URL: https://issues.apache.org/jira/browse/LOG4J2-1327
             Project: Log4j 2
          Issue Type: Bug
          Components: JMX
    Affects Versions: 2.5
            Reporter: Thomas Papke


The ConfigLocationUri is editable in the Mbean, but the behavior is a bit 
strange. If I type in the correct location e.g. {{file:/opt/tomcat 
/apache-tomcat/conf/log4j2.xml}} it correctly (re-)load the file once. But 
afterwards the “ConfigLocationUri” has automatically changed to 
{{file:/opt/tomcat/apache-tomcat/bin/file:/opt/tomcat/apache-tomcat/conf/log4j2.xml}}
 which is no longer a valid path. So it seems to log4j prefixes 
{{file:/opt/tomcat/apache-tomcat/bin/}} (this folder is the root folder where 
tomcat was started from) to my input, which is no longer a valid path.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to