java.io.IOException

Error scanning context central-ctx: java.lang.NullPointerException

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3

  • via Unknown by Rich Seddon,
  • via Unknown by Rich Seddon,
  • via Stack Overflow by sdoca
    ,
  • Stack trace

    • java.io.IOException: Error scanning context central-ctx: java.lang.NullPointerException at org.apache.maven.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:300) at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:903) at org.sonatype.nexus.index.DefaultIndexerManager.reindexAllRepositories(DefaultIndexerManager.java:810) at org.sonatype.nexus.tasks.ReindexTaskHandlerLegacy.reindexAllRepositories(ReindexTaskHandlerLegacy.java:47) at org.sonatype.nexus.tasks.AbstractIndexerTask.doRun(AbstractIndexerTask.java:80) at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:192) at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:338) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at org.apache.maven.index.context.IndexUtils.updateTimestamp(IndexUtils.java:175) at org.apache.maven.index.context.DefaultIndexingContext.updateTimestamp(DefaultIndexingContext.java:418) at org.apache.maven.index.context.DefaultIndexingContext.updateTimestamp(DefaultIndexingContext.java:408) at org.apache.maven.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:293) ... 13 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.