[LOG4J2-3484] environment variables are no longer resolved

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 2.17.2
• Component/s: Appenders

Environment

Openjdk11

OSX Monterey 12.3.1 (21E258)

• Assignee: Unassigned
• Reporter: Paul
• Created: 21/Apr/22 22:50
• Updated: 23/Apr/22 06:17
• Resolved: 22/Apr/22 20:52

Description

this used to worked in 2.16.0. I upgraded to 2.17.2 

    <RollingFile name="rollingFile" fileName="${env:DOMAIN_LOGS}/xxxxx.log" filePattern="$${sys:DOMAIN_LOGS}/$${date:yyyy-MM}/xxxxx-%d{MM-dd-yyyy}-%i.log.gz">

this bug seriously undercuts deployment models where log-location has to vary per environment.

 

log4J - once a workhorse that solved a core problem is now a liability to me. I'd roll back 5 versions if there wasn't the critical security flaw that's forced upgrades.

 

Hardcoding file-paths is simply not an option; this feature is unreliable, so maybe the oath forward is symlinks, and hardcode every path in sight.