Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Thu, 30 May 2013 09:04:20 +0000 (UTC)
From: "Daniel Lipp (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12650109.1369904572471.40093.1369904660102@arcas>
In-Reply-To: <JIRA.12650109.1369904572471@arcas>
References: <JIRA.12650109.1369904572471@arcas>
Subject: [jira] [Created] (JCR-3602) Don't swallow exception infos when
 logging RepositoryException in ACLProvider
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Daniel Lipp created JCR-3602:
--------------------------------

             Summary: Don't swallow exception infos when logging RepositoryException in ACLProvider
                 Key: JCR-3602
                 URL: https://issues.apache.org/jira/browse/JCR-3602
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core
    Affects Versions: 2.6.1
            Reporter: Daniel Lipp


org.apache.jackrabbit.core.security.authorization.principalbased.ACLProvider#getEditor(Session) and acModified(AccessControlModifications) use the following catch for RepositoryExceptions:

    } catch (RepositoryException e) {
        // should never get here
        log.warn("Internal error: ", e.getMessage());
    }

Unfortunately the format string doesn't contain a variable so the message of the caught RepositoryException is swallowed. As there's no stacktrace either, users will only get "Internal error: " in their logs.

--
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