You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "virajjasani (via GitHub)" <gi...@apache.org> on 2023/02/01 06:24:32 UTC

[GitHub] [logging-log4j2] virajjasani commented on issue #1227: ERROR No appender references provided to AsyncAppender: appenderRefs

virajjasani commented on issue #1227:
URL: https://github.com/apache/logging-log4j2/issues/1227#issuecomment-1411529807

   > Important note: The AsyncAppender can only be script configured using the [DOMConfigurator](https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/xml/DOMConfigurator.html).
   
   I see, thanks for the details. Looks like we might have to use AsyncAppenders together with RFA in that case (instead of applying RFA as appender ref to AsyncAppender).
   
   
   > Remark: Log4j 1.2 reached end-of-life almost 8 years ago. Several security vulnerabilities were discovered since then. You should not use it.
   
   I agree, we are migrating from Log4J1 to Log4J2 only. However, as part of the big migration, we would be working on several sub-tasks. Since we use log4j.properties (rather than xml), we had added RFA to AsyncAppender programmatically. In order to avoid using `org.apache.log4j.Logger` directly, we need to replace them with slf4j. Before we do that, first I wanted to replace code that does `asyncAppender.addAppender(rfaAppender)` with log4j.properties in log4j1. Once this sub-task is done, as part of the overall migration, we can directly replace all log4j.properties to log4j2.properties in one shot.
   Hence, I raised above question.
   
   Thanks


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org