[
https://issues.apache.org/jira/browse/JCR-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552557#comment-13552557
]
Jukka Zitting commented on JCR-3491:
------------------------------------
This might have broken the CI build, see
https://builds.apache.org/job/Jackrabbit-trunk/2028/
> Start the Repository immediatly in JCA Environment
> --------------------------------------------------
>
> Key: JCR-3491
> URL: https://issues.apache.org/jira/browse/JCR-3491
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jca
> Affects Versions: 2.2.13, 2.4.3, 2.5.2
> Reporter: Claus Köll
> Assignee: Claus Köll
> Fix For: 2.6
>
>
> With JCR-2523 the repository startup was changed to be lazy.
> It will be started on first access. This is a problem if you have a hot stand
> by cluster member.
> The repository will be started on first access and so the cluster sync is not
> up to date because reposiotry is not startet on server startup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
