Skip to content

Log level mismatch in LdapFilterPlugin.java #2751

@yiming-tang-cs

Description

@yiming-tang-cs

In the example below, line 92 uses a log level of FINER in a logging statement that describes a failure that happens under a certain condition. In contrast, line 99 contains an informational log but has the same level of FINER. This contrast in severity is pronounced by the high-level exception thrown on line 96. Should the level in line 92 be greater than FINER?

try {
if ((records = getLdapProvider().lookupLdapContent(null, expandedFilter, dn)) == null) {
LOGGER.log(Level.FINER, "failed to get content for user from LDAP server");
return;
}
} catch (LdapException ex) {
throw new AuthorizationException(ex);
}
LOGGER.log(Level.FINER, "got {0} records", records.size());

Filed in conjunction with @orenwf and @khatchad.

Activity

vladak

vladak commented on Apr 18, 2019

@vladak
Member

Definitely, the log levels in authorization plugins are not very consistent in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @vladak@yiming-tang-cs

        Issue actions

          Log level mismatch in LdapFilterPlugin.java · Issue #2751 · oracle/opengrok