You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/06/10 15:26:21 UTC
[jira] [Created] (SLING-5779) LuceneIndexProviderService sometimes
is not configured
Robert Munteanu created SLING-5779:
--------------------------------------
Summary: LuceneIndexProviderService sometimes is 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)