[
https://issues.apache.org/jira/browse/LOG4J2-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-102.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta3
Fix applied in revision 1400349. Please verify then close.
> Bad priority in Syslog messages
> -------------------------------
>
> Key: LOG4J2-102
> URL: https://issues.apache.org/jira/browse/LOG4J2-102
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
> Affects Versions: 2.0-beta2
> Reporter: Emanuele Colombo
> Priority: Critical
> Fix For: 2.0-beta3
>
>
> In class org.apache.logging.log4j.core.net.Priority the method getPriority
> returns a bad priority when used for Syslog messages (the only usage at the
> moment). The bug is in the statement:
> facility.getCode() << 3 + Severity.getSeverity(level).getCode()
> That's because the operator "+" takes precedence over "<<", and so the
> facility code isn't shifted by 3 but by "3 +
> Severity.getSeverity(level).getCode()".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
