You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2016/08/02 14:55:20 UTC
[jira] [Closed] (LOG4J2-1491) Exception when mixing varargs and
non-varargs overloads
[ https://issues.apache.org/jira/browse/LOG4J2-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory closed LOG4J2-1491.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.6.2
> 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
> Fix For: 2.6.2
>
>
> 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