[ 
https://issues.apache.org/jira/browse/SLING-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328940#comment-15328940
 ] 

Carsten Ziegeler edited comment on SLING-5779 at 6/14/16 5:01 AM:
------------------------------------------------------------------

OSGi is dynamic and therefore the order must not matter. If the configuration 
is set later, the system should still work as expected.
The OSGi Installer has no knowledge of the artifacts it's handling (if we 
neglect the fact that it knows about the built-in bundle support), so this is 
delegated to plugins - whenever those plugins are available.
If your app really needs ordering, make sure that config admin and the 
configuration support is started before the bundles which require them. 


was (Author: cziegeler):
OSGi is dynamic and therefore the order must not matter. If the configuration 
is set later, the system should still work as expected.
The OSGi Installer has no knowledge of the artifacts it's handling (if we 
neglect the fact that it knows about the built-in bundle support), so this is 
delegated to plugins - whenever those plugins are available.
If you app really needs ordering, make sure that config admin and the 
configuration support is started before the bundles which require them. 

> 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)

Reply via email to