Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Wed, 2 Nov 2011 15:11:32 +0000 (UTC)
From: "Thomas Mueller (Updated) (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <441115758.50650.1320246692367.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1161444633.19905.1318840451799.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (JCR-3116) Cluster Node ID should be trimmed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Mueller updated JCR-3116:
--------------------------------

    Fix Version/s: 2.2.10
    
> Cluster Node ID should be trimmed
> ---------------------------------
>
>                 Key: JCR-3116
>                 URL: https://issues.apache.org/jira/browse/JCR-3116
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: clustering, config, jackrabbit-core
>    Affects Versions: 2.2.9, 2.3.1
>            Reporter: Julian Sedding
>            Assignee: Thomas Mueller
>            Priority: Trivial
>             Fix For: 2.2.10, 2.4
>
>         Attachments: JCR-3116.patch
>
>
> If the cluster node ID is not configured in repository.xml, it is read from the file cluster_node.id instead. In case this file is edited by hand, some editors (e.g. vi) insert a trailing newline character ("\n"). This leads to the cluster node ID to contain a blank character. While I don't expect this to cause any issues, it is inconvenient for debugging and also introduces line-breaks in log files. I suggest to trim the cluster node ID, so only non-blank characters are used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira