[
https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775609#comment-13775609
]
Eric Schwarzenbach commented on LOG4J2-378:
-------------------------------------------
It looks like the "myapp.log" file was somehow being caused by a different
webapp. Something really odd is going on here. I had two webapps deployed, one
was a previous iteration of the same app (still using log4j beta8, and still
logging to "...$\{sys:application-name\}.log". Getting rid of the old webapp
causes "myapp.log" to no longer be created. Note the the old webapp did not
have the name "myapp" anywhere in it at all, that was completely new to this
new build of my app.
Further though the same messages were logged in "My Web Application.log" and
"myapp.log" the _format_ was slightly different. While "My Web Application.log"
had lines like:
2013-09-23 15:39:39,644 INFO a.b.c.d.SomeServiceImpl [pool-2-thread-1]
SomeServiceImpl created
"myapp.log" had lines like
2013-09-23 15:39:51,419 INFO ? [pool-2-thread-1] SomeServiceImpl created
I'm not making this stuff up, I promise!
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
