You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2022/02/19 08:34:00 UTC

[jira] [Resolved] (LOG4J2-3397) Log4j2 writing logs to already rolled file when deployed multiple wars on jboss

     [ https://issues.apache.org/jira/browse/LOG4J2-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-3397.
---------------------------------
    Resolution: Not A Bug

Marking as resolved. Please close if you agree with this assessment.

> Log4j2 writing logs to already rolled file when deployed multiple wars on jboss
> -------------------------------------------------------------------------------
>
>                 Key: LOG4J2-3397
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3397
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.17.1, 2.17.0
>         Environment: JBOSS-EAP -7.3
> LOG4j 2.17.1
>            Reporter: Bindra Bambharoliya
>            Priority: Major
>
> h4. Log4j2 writing logs to already rolled file When deployed mutiple wars on jboss and all war using same file to write the logs.  
> h4. We have configured log4j2.xml in standalone.xml file for central looging system for entire application. BUt then Log4j2 writing logs to already rolled file.
> Kindly help on configuration or how to use it with JBOSS central logging



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