[
https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091143#comment-16091143
]
Ralph Goers commented on LOG4J2-1980:
-------------------------------------
That would mean that weblogic.Name is not actually a system property. Did you
customize the startup script? From what I am reading it is set there.
> log4j2.properties substitution ${} ie.${weblogic.Name} not working in
> WebLogic 12.1.3
> -------------------------------------------------------------------------------------
>
> Key: LOG4J2-1980
> URL: https://issues.apache.org/jira/browse/LOG4J2-1980
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.2
> Environment: OS : Red Hat
> Enterprise Linux Server release 6.7 (Santiago)
> java version : 1.8.0_131
> WebLogic Server Version : 12.1.3.0.0
> Log4J jar : log4j-core-2.6.2.jar
> Reporter: Suyog Chinche
>
> We are using $\{weblogic.Name}, which is weblogic system property used to
> fetch weblogic server name.
> This is not working in log4j2, whereas it was working in log4j earlier
> version.
> <property file>
> appender.userLog.fileName=/u01/app/product/fmw/logs/$\{weblogic.Name}_xai-user.log
> appender.userLog.filePattern=/u01/app/product/fmw/logs/$\{weblogic.Name}_xai-user.log.%d{yyyy-MM-dd}
> </property file>
> With the help of above log4j propertyfile, it is creating
> $\{weblogic.Name}_xai-user.log file in /u01/app/product/fmw/logs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
