java.lang.NullPointerException

null

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web20370

  • null
  • via GitHub by todoubaba
    , 1 year ago
    null
  • null
  • Stack trace

    • java.lang.NullPointerException: null at org.sonatype.timeline.internal.DefaultTimeline.purgeFromIndexer(DefaultTimeline.java:241)[na:na] at org.sonatype.timeline.internal.DefaultTimeline.purge(DefaultTimeline.java:197)[na:na] at org.sonatype.nexus.timeline.DefaultNexusTimeline.purgeOlderThan(DefaultNexusTimeline.java:183)[na:na] at org.sonatype.nexus.timeline.tasks.PurgeTimeline.doRun(PurgeTimeline.java:109)[na:na] at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:177)[nexus-core-2.6.4-02.jar:2.6.4-02] at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:483)[nexus-scheduler-2.6.4-02.jar:2.6.4-02] at org.sonatype.nexus.threads.MDCAwareCallable.call(MDCAwareCallable.java:44)[nexus-core-2.6.4-02.jar:2.6.4-02] at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)[shiro-core-1.2.2.jar:1.2.2] at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)[shiro-core-1.2.2.jar:1.2.2] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[na:1.7.0_25] at java.util.concurrent.FutureTask.run(FutureTask.java:166)[na:1.7.0_25] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[na:1.7.0_25] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[na:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[na:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[na:1.7.0_25] at java.lang.Thread.run(Thread.java:724)[na:1.7.0_25]

    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

    You’re the first here who have seen this exception.