You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Piotr Karwasz (Jira)" <ji...@apache.org> on 2024/04/24 22:08:00 UTC
[jira] [Resolved] (LOG4J2-3455) Log4j 1.x 2.17.2 bridge - Thread specific Log Level Threshold doesn't work
[ https://issues.apache.org/jira/browse/LOG4J2-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Karwasz resolved LOG4J2-3455.
-----------------------------------
Resolution: Information Provided
> Log4j 1.x 2.17.2 bridge - Thread specific Log Level Threshold doesn't work
> --------------------------------------------------------------------------
>
> Key: LOG4J2-3455
> URL: https://issues.apache.org/jira/browse/LOG4J2-3455
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.17.2
> Reporter: Pooja Pandey
> Priority: Major
> Attachments: CustomLogger.java, CustomLoggerFactory.java, CustomMultiProcessRollingAppender.java, ThreadLevelLogThresholdTest.java, customlog.properties
>
>
> In our application we have migrated from log4j1.x to log4j1.x 2.17.2 bridge. With bridge 2.17.2/2.17.3-SNAPSHOT, thread specific log level threshold doesn't work which used to work earlier with log4j1.x. We had achieved this feature by overriding getEffectiveLevel(), but now this doesn't work anymore with log4j1.x bridge since the method getEffectiveLevel() is not getting invoked to set effective level.
>
> For reference, Java class files for Custom Logger, Custom Multiprocess Rolling Appender and Test program are attached along with cutom log4j properties file.[^CustomLogger.java][^customlog.properties][^ThreadLevelLogThresholdTest.java]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)