You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominique Pfister (JIRA)" <ji...@apache.org> on 2008/09/12 13:35:48 UTC
[jira] Created: (JCR-1734) Generated cluster node id should be
persisted
Generated cluster node id should be persisted
---------------------------------------------
Key: JCR-1734
URL: https://issues.apache.org/jira/browse/JCR-1734
Project: Jackrabbit
Issue Type: Bug
Affects Versions: core 1.4.5
Reporter: Dominique Pfister
Assignee: Dominique Pfister
Priority: Minor
If no cluster node id is specified in the configuration, a cluster node id is automatically generated. This id is never persisted, so after another startup a new, probably different cluster node id is used. Instead, an automatically generated cluster id should be persisted inside the repository home.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1734) Generated cluster node id should be
persisted
Posted by "Dominique Pfister (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominique Pfister updated JCR-1734:
-----------------------------------
Component/s: clustering
> Generated cluster node id should be persisted
> ---------------------------------------------
>
> Key: JCR-1734
> URL: https://issues.apache.org/jira/browse/JCR-1734
> Project: Jackrabbit
> Issue Type: Bug
> Components: clustering
> Affects Versions: core 1.4.5
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
> Priority: Minor
>
> If no cluster node id is specified in the configuration, a cluster node id is automatically generated. This id is never persisted, so after another startup a new, probably different cluster node id is used. Instead, an automatically generated cluster id should be persisted inside the repository home.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1734) Generated cluster node id should be
persisted
Posted by "Dominique Pfister (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominique Pfister resolved JCR-1734.
------------------------------------
Resolution: Fixed
Fixed in revision 695821.
> Generated cluster node id should be persisted
> ---------------------------------------------
>
> Key: JCR-1734
> URL: https://issues.apache.org/jira/browse/JCR-1734
> Project: Jackrabbit
> Issue Type: Bug
> Components: clustering
> Affects Versions: core 1.4.5
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
> Priority: Minor
>
> If no cluster node id is specified in the configuration, a cluster node id is automatically generated. This id is never persisted, so after another startup a new, probably different cluster node id is used. Instead, an automatically generated cluster id should be persisted inside the repository home.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1734) Generated cluster node id should be
persisted
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1734:
-------------------------------
Fix Version/s: 1.5
Tagging this for 1.5, as it seems a bit complex for inclusion in jackrabbit-core 1.4.6. Let me know if we should have this also in the maintenance branch.
> Generated cluster node id should be persisted
> ---------------------------------------------
>
> Key: JCR-1734
> URL: https://issues.apache.org/jira/browse/JCR-1734
> Project: Jackrabbit
> Issue Type: Bug
> Components: clustering
> Affects Versions: core 1.4.5
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
> Priority: Minor
> Fix For: 1.5
>
>
> If no cluster node id is specified in the configuration, a cluster node id is automatically generated. This id is never persisted, so after another startup a new, probably different cluster node id is used. Instead, an automatically generated cluster id should be persisted inside the repository home.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.