[
https://issues.apache.org/jira/browse/SLING-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329297#comment-15329297
]
Carsten Ziegeler commented on SLING-5779:
-----------------------------------------
I've discussed this with [~chetanm] offline a little bit. Now, the issue here
is that the support for configurations is available after the OSGi installer
already started its work. The installer is happily installing bundles and only
once that is done completely it picks up the configuration support which was
registered while it was installing the bundles. This then results in
unnecessary restarts of components. I see this point, we can optimize here:
We could add a (framework) configuration to the OSGi installer which lists
required plugins - similar to what we do with the resource resolver factory and
the jcr provider. So the OSGi installer can be configured to wait for the
configuration support and only start actions once everything is in place. I
think this makes sense as it avoid churn in the system.
However, the general statement applies that components should be prepared for
configurations arriving "later" or being changed at runtime. There are various
mechanisms to deal with these situations (require policy, implementing modified
etc.)
> LuceneIndexProviderService is sometimes not configured
> ------------------------------------------------------
>
> Key: SLING-5779
> URL: https://issues.apache.org/jira/browse/SLING-5779
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Reporter: Robert Munteanu
> Fix For: Launchpad Builder 9
>
> Attachments: error.log.gz, stdout.log.gz
>
>
> (Setting version to Launchpad for now until we find out the root cause).
> From time to time I see the launchpad failing to start properly. The first
> error that is visible is {noformat}10.06.2016 18:18:48.826 *ERROR*
> [OsgiInstallerImpl] org.apache.jackrabbit.oak-lucene
> [org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexProviderService(31)]
> The activate method has thrown an exception (java.lang.NullPointerException:
> Index directory cannot be determined as neither index directory path
> [localIndexDir] nor repository home [repository.home] defined)
> java.lang.NullPointerException: Index directory cannot be determined as
> neither index directory path [localIndexDir] nor repository home
> [repository.home] defined
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:236){noformat}
> That's weird since the provisioning model holds all the configurations and
> the relevant bundles are present in the {{:boot}} feature → Start Level 1.
> My launchpad jar was built from r1747733 ( but of course SNAPSHOT
> dependencies mean that someone else building the launchpad will not get the
> same exact output ).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
