[
https://issues.apache.org/jira/browse/LOG4J2-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344146#comment-15344146
]
Remko Popma commented on LOG4J2-1435:
-------------------------------------
I think you need to change your configuration from
{code}
<logger name="org.springframework">
<level value="WARN" />
</logger>
<logger name="org.jboss">
<level value="WARN" />
</logger>
<logger name="org.hibernate">
<level value="OFF" />
</logger>
<logger name="com.company.project.eligibility">
<level value="WARN" />
</logger>
{code}
to
{code}
<logger level="WARN" name="org.springframework" />
<logger level="WARN" name="org.jboss" />
<logger level="OFF" name="org.hibernate" />
<logger level="WARN" name="com.company.project.eligibility" />
{code}
> Log4j2 writing logs to already rolled file
> ------------------------------------------
>
> Key: LOG4J2-1435
> URL: https://issues.apache.org/jira/browse/LOG4J2-1435
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators, Performance Benchmarks
> Affects Versions: 2.6.1
> Environment: OS : Linux
> Weblogic: 10.3.6.0
> JDK: 1.7.0_55
> Log4j version tested: 2.3 and 2.6.1
> Reporter: Prashant
> Priority: Critical
> Attachments: Capture.PNG, Capture2.PNG, log4j.xml
>
>
> Recently we have migrated from log4j 1.x to 2.6.1
> I am seeing loggers are being written to rolled file along with main log file.
> This is observed mainly if I am pushing load of 400k records.
> PFA log4j xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
