Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1436603205.1224060104302.JavaMail.jira@brutus>
Date: Wed, 15 Oct 2008 01:41:44 -0700 (PDT)
From: "Felix Meschberger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-1812) WorkspaceUpdateChannel.updateCommitted
 logs too much
In-Reply-To: <1992675364.1224059984546.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated JCR-1812:
-----------------------------------

    Attachment: JCR-cluster-update-log.patch

Proposed patch, which also includes making use of SLF4Js log call optimization for not concatenating strings if not needed.

> WorkspaceUpdateChannel.updateCommitted logs too much
> ----------------------------------------------------
>
>                 Key: JCR-1812
>                 URL: https://issues.apache.org/jira/browse/JCR-1812
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering
>    Affects Versions: core 1.4.2
>            Reporter: Felix Meschberger
>         Attachments: JCR-cluster-update-log.patch
>
>
> On each cluster record update, an info message is logged.
> I think this is too much and logging should be reduced to the DEBUG level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.