[jira] Commented: (JCR-1694) System properties does not get replaced in a Cluster configuration

["Alexander Klimetschek (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621490#action_12621490 ] 

Alexander Klimetschek commented on JCR-1694:
--------------------------------------------

For clustering, you can set the system property "org.apache.jackrabbit.core.cluster.node_id" instead of setting the id attribute in the Cluster config element. See http://wiki.apache.org/jackrabbit/Clustering.

We could have multiple ways of setting the id dynamically, but I would prefer to have only one way of doing this in this case. WDYT?

> System properties does not get replaced in a Cluster configuration
> ------------------------------------------------------------------
>
>                 Key: JCR-1694
>                 URL: https://issues.apache.org/jira/browse/JCR-1694
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: config
>    Affects Versions: core 1.4.5
>            Reporter: fabrizio giustina
>         Attachments: JCR-1694-fix.diff, JCR-1694-testcase.diff
>
>
> Since JCR-1304 has been added to jackrabbit 1.4 I guess this should be reported as a bug...
> Still not debugged deeply, but if I try to configure a Cluster using:
> <Cluster id="${server}" syncDelay="10">
> after setting a "server" system property I expect to have the cluster initialized properly using the value of such property... I just realized that my cluster node gets initialized with the final value of "${server}" instead :(
> Cluster config is a very good place where to use system properties, since all the configuration is usually identical between cluster nodes while the "id" property must be different...
> Is there anything I missed/did wrong in my configuration?

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