[
https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716247#comment-13716247
]
Sudharma Puranik commented on LOG4J2-314:
-----------------------------------------
For routing I can make for specific Summary file {noformat}<Route
appender-ref="SUMMARY_ALL" key="Summary"/>{noformat} but the problem is , I
have to add into the ThreadContext with requestID --> Summary. So instead what
I decided was that let by default Routing be the one with requestId and I
added{noformat} <appender-ref ref="SUMMARY_ALL" />{noformat} into my Async
Appender. Only the problem with this is that once I remove the requestId from
the context, the next logging creates an empty file with **dump-${ctx** .
Can we have a feasibility that any key removed from ThreadContext should
internally stop routing If any further logging? Because Default also will
expect something as value.
And you can mark this as resolved. Thanks a lot for your help.
> Multiple thread creation problem with AsyncAppender
> ---------------------------------------------------
>
> Key: LOG4J2-314
> URL: https://issues.apache.org/jira/browse/LOG4J2-314
> Project: Log4j 2
> Issue Type: Question
> Components: Appenders, Configurators
> Reporter: Sudharma Puranik
> Attachments: asyncAppendThread.png, log4j2.xml, loggerThread.png,
> TestAppender.zip
>
>
> I have a log4j2.xml configuration file from which I am getting the Logger,
> attached is the snapshot. when my logger is created a new thread is created.
> Programmatically,I create a RollingFileAppender and attach the it to
> AsyncAppender . I attach the Async Appender to the configuration of the
> log4j.xml, And when I start the Async Appender again a new thread is created.
> Is this a bug? because I get a logger a new thread is generated and when I
> create a async appender another thread is created and both are doing the same
> job.
> Also there is already a asyncappender in my log4j2.xml and I am creating one
> via program. Will this cause a problem? I did this because I am currently
> unable to hook my programmatically created appender to the AsyncAppender
> defined in log4j2.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
