[
https://issues.apache.org/jira/browse/LOG4J2-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603245#comment-17603245
]
Abhilash commented on LOG4J2-3592:
----------------------------------
In our company the 2.17.1 version or prior will not be available in repository
so we don’t have any options but to fix it by October 15. Any help on this
would be highly appreciated.
> Log4j 2.17.2 version not able to resolve system variable in log4j2.xml file
> ---------------------------------------------------------------------------
>
> Key: LOG4J2-3592
> URL: https://issues.apache.org/jira/browse/LOG4J2-3592
> Project: Log4j 2
> Issue Type: Question
> Reporter: Abhilash
> Priority: Blocker
>
> Hi Team,
>
> We were using log4j 2.17.1 version and we were not facing any issue while
> resolving the system variable placeholder in log4j2.xml file.
>
> Post upgrading to 2.17.2 or 2.18.0 we are the log4 lib not replacing the
> place holder with provided system variable.
>
> our configuration:
> *log4j2.xml*
> <Properties>
> <Property name="logpath">${bundle:config:aap.LogPath}</Property>
> </Properties>
>
> *config.properties*
> LogPath=/logs/appName/{*}${sys:appEnvironment}/${sys:instanceName}{*}
>
> The above *${sys:appEnvironment} and* *${sys:instanceName}* are not resolving
> after 2.17.2 onwards.
>
> There is mandate that we no longer can use the 2.17.1 version in our company
> due to security reasons so using 2.17.2 or above is a must but we are blocked
> due to the above filepath issue.
>
> Kindly guide us on this to fix it. Thank you. **
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
