[ 
https://issues.apache.org/jira/browse/LOG4J2-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478198#comment-17478198
 ] 

Carter Kozak commented on LOG4J2-3317:
--------------------------------------

Can you please provide the full contents of your configuration?
This document provides some details about the changes: 
[https://github.com/apache/logging-log4j2/blob/release-2.x/docs/2.17.0-interpolation.md]

Only one level of interpolation is handled, so if you're referencing a property 
from within a <Route> and that property includes something like 
${ctx:SomeVariable}, it will not recursively be evaluated. You may need to 
inline the value of the property into the route itself.
Without either a reproducer, or minimally a full copy of your configuration, I 
cannot provide concrete advice.

> After 2.17.1 upgarde, Route appenders with dynamic file writing are not 
> working . 
> ----------------------------------------------------------------------------------
>
>                 Key: LOG4J2-3317
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3317
>             Project: Log4j 2
>          Issue Type: Bug
>         Environment: spring boot log4j2.
> deployed on wildfly server.
>            Reporter: Srinivasa Babu
>            Priority: Major
>
> Hello Sir,
> With log4j2 2.13.3 , Route appenders with context pattern checks for dynamic 
> file writing are working fine. After 2.17.1 the functionality is broken.
> I have upgraded to 2.17.1 and our java code, I am setting the ROUTINGKEY in 
> threadcontext map. Also i set the system properties,  
> log4j2.enableJndiLookup, log4j2.enableJndiJms, and 
> log4j2.enableJndiContextSelector to true for all said tags after 2.17.1 
> upgrade.
> When I check output file, its not writing the logs to Route File what we 
> specify but general RollingFile logger appenders are working fine. Please let 
> me know if you have faced this issue or any mitigation plan? Please let me 
> know if you want any logs and i will share those if there is any specific 
> procedure given. 
>  
> Calling the below Route from Async logging.
> here my example xml used the same as given in log4j2 documentaion.
> <Route key="$${ctx:ROUTINGKEY}">
> <RollingFile name="Rolling-default" fileName="logs/default.log"
> filePattern="./logs/${date:yyyy-MM}/default-%d\{yyyy-MM-dd}-%i.log.gz">
> <PatternLayout>
> <pattern>%d\{ISO8601} [%t] %p %c\{3} - %m%n</pattern>
> </PatternLayout>
> <Policies>
> <TimeBasedTriggeringPolicy interval="6" modulate="true" />
> <SizeBasedTriggeringPolicy size="10 MB" />
> </Policies>
> </RollingFile>
> </Route>
> <Route>
> <RollingFile name="Rolling-${ctx:ROUTINGKEY}" 
> fileName="logs/other-${ctx:ROUTINGKEY}.log"
> filePattern="./logs/${date:yyyy-MM}/${ctx:ROUTINGKEY}{-}other{-}%d\{yyyy-MM-dd}-%i.log.gz">
> <PatternLayout>
> <pattern>%d\{ISO8601} [%t] %p %c\{3} - %m%n</pattern>
> </PatternLayout>
> <Policies>
> <TimeBasedTriggeringPolicy interval="6" modulate="true" />
> <SizeBasedTriggeringPolicy size="10 MB" />
> </Policies>
> </RollingFile>
> </Route>
> </Routes>
> </Routing>
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to