[
https://issues.apache.org/jira/browse/SLING-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329210#comment-15329210
]
Chetan Mehrotra commented on SLING-5779:
----------------------------------------
Depends on usecase. We have certain features which we do not enable by default
in Oak. However for certain apps which we run on Oak we need to enable those
features. So I do not see a requirement to make config as required.
> 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)