[LOG4J2-971] Another bad priority in Syslog messages

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.3
• Component/s: Layouts
• Labels: syslog syslogappender
• Assignee: Unassigned
• Reporter: Paul D Johe
• Created: 04/Mar/15 15:13
• Updated: 10/Mar/15 15:38
• Resolved: 04/Mar/15 19:22

Description

The method org.apache.logging.log4j.core.net.Priority#getValue() has the same problem as previously mentioned in issue LOG4J2-102:

Incorrect:

public int getValue() {
        return facility.getCode() << 3 + severity.getCode();
    }

Correct:

public int getValue() {
        return (facility.getCode() << 3) + severity.getCode();
    }

Perhaps also clean up the code so that the logic is only implemented in one place:

    public static int getPriority(final Facility facility, final Level level) {
        return new Priority(facility, Severity.getSeverity(level)).getValue();
    }

Issue Links

• is related to: LOG4J2-102 Bad priority in Syslog messages