logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Chadwick (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1491) Exception when mixing varargs and non-varargs overloads
Date Tue, 02 Aug 2016 11:54:20 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403833#comment-15403833
] 

Nick Chadwick commented on LOG4J2-1491:
---------------------------------------

Ah yes, I was using a 2.6.1-SNAPSHOT version. It is working with 2.6.2. Thanks for the quick
response, and apologies for the error

> Exception when mixing varargs and non-varargs overloads
> -------------------------------------------------------
>
>                 Key: LOG4J2-1491
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1491
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.6.1
>            Reporter: Nick Chadwick
>
> There is a bug with the way parameters are swapped in and out of reusable parameterised
messages, if there is a mixture of log statements using varargs and non-varargs overloads.
> To reproduce, run the following and observe that the third log statement throws an exception.
>         logger.info("Test {}", new Object[] { 1 });
>         logger.info("Test {} {}", Unbox.box(1), Unbox.box(2));
>         logger.info("Test {} {}", Unbox.box(1), Unbox.box(2));



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message