[jira] [Updated] (LOG4J2-378) Logging generates file named ${sys on some systems

["Eric Schwarzenbach (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Schwarzenbach updated LOG4J2-378:
--------------------------------------

    Affects Version/s: 2.0-beta9

Bump...

I know I noted some mistakes in my first comments about the bug still existing in beta9, but the basic problem still occurs:

using ${web:servletContextName}.log in an appender file name still winds up creating a 0 byte file named ${web:servletContextName}.log (under linux), and it also creates one using the value from the display-name element of the web.xml rather than the name of the war file / webapp folder.

> Logging generates file named ${sys on some systems
> --------------------------------------------------
>
>                 Key: LOG4J2-378
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-378
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.0-beta8, 2.0-beta9
>         Environment: Issues occurs on Win7/64 system under Tomcat 7.0.42 / Oracle JDK 1.7.0_25; fails to occur on RHEL 5.2 system under Tomcat 7.0.26 / Oracle JDK 1.7.0_03
>            Reporter: Eric Schwarzenbach
>
> In a webapp I'm setting a system property in my apps ServletContextListener, and using that system property in my log4j2.xml file, like so:
> {code}
> <appender type="FastFile" name="File" fileName="${sys:catalina.home}/logs/${sys:application-name}.log">
> {code}
> On my Windows machine, a log file named "${sys." (always 0 bytes) is being created instead of a log file with the application-name. The same war deployed on one of our linux servers does not create a ${sys." file and instead creates a log file with the intended application-name. 
> I should note that the files DO appear in the directory that sys:catalina.home should resolve to. They appear elsewhere when I don't use sys:catalina.home so I'm quite sure that this variable is resolving correctly and it is the sys:application-name which is the problem.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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