-
Notifications
You must be signed in to change notification settings - Fork 141
Open
Description
I see the following stack trace in my logs:
java.lang.NullPointerException: null
at redis.RedisCluster.$anonfun$onConnectStatus$1(RedisCluster.scala:44)
at redis.RedisCluster.$anonfun$onConnectStatus$1$adapted(RedisCluster.scala:39)
at redis.actors.RedisWorkerIO.onConnected(RedisWorkerIO.scala:70)
at redis.actors.RedisWorkerIO$$anonfun$connecting$1.applyOrElse(RedisWorkerIO.scala:57)
at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:269)
at akka.actor.Actor.aroundReceive(Actor.scala:537)
at akka.actor.Actor.aroundReceive$(Actor.scala:535)
at redis.actors.RedisWorkerIO.aroundReceive(RedisWorkerIO.scala:15)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:580)
at akka.actor.ActorCell.invoke(ActorCell.scala:548)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:270)
at akka.dispatch.Mailbox.run(Mailbox.scala:231)
at akka.dispatch.Mailbox.exec(Mailbox.scala:243)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
This is with both version 2.6.1 and 2.7.0 of play-redis.
Play version is 2.8.5.
Scala version is 2.13.8.
This is running in an AWS cloud.
Expected behavior is the absence of null pointer exceptions.
To reproduce, run my entire non-open source in the AWS account I'm not going to share, I guess :|
I haven't noticed correlations with anything.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels