maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Closed] (MINDEXER-44) NPE from DefaultSearchEngine.doSearchWithCeiling
Date Sun, 06 Sep 2015 20:51:57 GMT


Michael Osipov closed MINDEXER-44.
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> NPE from DefaultSearchEngine.doSearchWithCeiling
> ------------------------------------------------
>                 Key: MINDEXER-44
>                 URL:
>             Project: Maven Indexer
>          Issue Type: Bug
>    Affects Versions: 4.1.1
>            Reporter: Jesse Glick
>            Priority: Minor
> reports
which shows
> {code}
> java.lang.NullPointerException
> 	at org.apache.maven.index.DefaultSearchEngine.doSearchWithCeiling(
> 	at org.apache.maven.index.DefaultSearchEngine.searchFlat(
> 	at org.apache.maven.index.DefaultSearchEngine.searchFlatPaged(
> 	at org.apache.maven.index.DefaultSearchEngine.searchFlatPaged(
> {code}
> This comes after some index download problems like
> {code}
> Resource nexus-maven-repository-index.gz does not exist
> 	at org.apache.maven.index.updater.WagonHelper$WagonFetcher.retrieve(
> 	at org.apache.maven.index.updater.WagonHelper$WagonFetcher.retrieve(
> 	at org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(
> 	at org.apache.maven.index.updater.DefaultIndexUpdater.access$300(
> 	at org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(
> 	at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(
> 	at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(
> {code}
> It seems that the {{DefaultIndexingContext.indexSearcher}} is null, for whatever reason,
and {{searchFlatPaged}} is not verifying that it has been passed a valid context and does
not attempt to fix an invalid context, perhaps using {{openAndWarmupReaders}}.
> Probably the caller is at fault for attempting a search on a context with no valid index,
but this ought to be reported more clearly than with an NPE several calls down the stack,
and there should be some documented method for checking that a context is somehow complete
and ready for use.

This message was sent by Atlassian JIRA

View raw message