FrankCy commented on issue #2582: URL: https://github.com/apache/logging-log4j2/issues/2582#issuecomment-2111876623
> I don't actually see a problem being stated anywhere here. What exactly is wrong? Hello, the program uses both rocketmq and redis and uses the topology refresh feature of redis, which has a dependency on lettuce-core, and the program is using log4j as the log collection output. We set ERROR in the log output of rocketmq component and output the logs to rocketmq-client.log, because we set the rocketmq log output level to ERROR, normally rocketmq-client.log will only print ERROR about rocketmq's logs, but the real Normally, rocketmq-client.log would only print ERROR logs for rocketmq, but in reality, it outputs DEBUG logs for lettuce-core, which is a dependency of spring-boot-stater-data-redis. It should not be in this log file. It's not clear why it arises, is it something to do with the order in which the component's logging dependencies are loaded? Translated with www.DeepL.com/Translator (free version) -- 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-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
