[ 
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piotr Karwasz resolved LOG4J2-3419.
-----------------------------------
    Fix Version/s: 2.17.3
       Resolution: Fixed

[~TukeshK], [~ragini]: I have generated a new snapshot of version 2.17.3. Can 
you check if this solves your problem?

Custom Log4j 1.x levels should work out-of-the-box (like {{UtilLoggingLevel}}). 
On the other hand, if you want to use a custom Log4j 2.x level in the Log4j 1.x 
configuration file you must:
# Take care to declare the level *before* the configuration is read,
# Use the {{level_name#org.apache.logging.log4j.Level}} syntax in the 
configuration file.

> Unable to create custom logging level using log4j 2 Bridge API
> --------------------------------------------------------------
>
>                 Key: LOG4J2-3419
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3419
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Log4j 1.2 bridge
>    Affects Versions: 2.17.1
>         Environment: Using log4j 2 bridge API: log4j-1.2-api-2.17.1.jar
>            Reporter: Ragini Gawande
>            Assignee: Piotr Karwasz
>            Priority: Blocker
>             Fix For: 2.17.3
>
>         Attachments: DemoCustom.zip
>
>
> Unable to create custom logging level using log4j 2 Bridge API
> Following did not create a custom logging level
> *public static final int FINE_INT = 13000;*
> *public static final Level FINE = new Level(FINE_INT, "FINE", 7);* 
>  
> Using FINE logging level is considered to be DEBUG level by default while 
> printing it
> *Adding log:*
> log.log({*}Level.FINE{*},"PRINT: Level.FINE log");
>  
> *Expected log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *FINE* - PRINT: 
> Level.FINE log 
>  
> *Actual log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *DEBUG* - PRINT: 
> Level.FINE log 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to