java.lang.NullPointerException

Stack Overflow | jalv1039 | 6 months ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    `activator testOnly` does not work as expected

    GitHub | 9 months ago | ShahBinoy
    java.lang.NullPointerException: null, took 2.999 sec [error] at controllers.auth.LoginController.authenticate(LoginController.java:51)

    Root Cause Analysis

    1. java.lang.NullPointerException

      No message provided

      at com.test.C.endActor()
    2. com.test
      C$$anonfun$scheduleEndActor$2.apply$mcV$sp
      1. com.test.C.endActor(Test.scala:90)
      2. com.test.C$$anonfun$scheduleEndActor$2.apply$mcV$sp(Test.scala:88)
      2 frames
    3. Akka Actor
      ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec
      1. akka.actor.Scheduler$$anon$2.run(Scheduler.scala:78)
      2. akka.actor.LightArrayRevolverScheduler$$anon$2$$anon$1.run(LightArrayRevolverScheduler.scala:104)
      3. akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:39)
      4. akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:409)
      4 frames
    4. Scala
      ForkJoinWorkerThread.run
      1. scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
      2. scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
      3. scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
      4. scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
      4 frames