jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3116) Cluster Node ID should be trimmed
Date Tue, 08 Nov 2011 12:52:52 GMT

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

Jukka Zitting updated JCR-3116:
-------------------------------

    Fix Version/s:     (was: 2.4)
                   2.3.3
       Issue Type: Bug  (was: Improvement)
    
> Cluster Node ID should be trimmed
> ---------------------------------
>
>                 Key: JCR-3116
>                 URL: https://issues.apache.org/jira/browse/JCR-3116
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          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.3.3
>
>         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

        

Mime
View raw message