question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Redis connection problem

See original GitHub issue

Reporting a bug

  1. Version of play-redis 1.6.1
  2. Version of Play 2.6.x
  3. Describe the actual behavior, follow the same scenario Our version of redis is docker run -d --name redis-cache -p 6379:6379 redis:4-alpine We have configured the play-redis like you said on the wiki. After this, we try to do a cache.get() and the system is blocked for 1 min more or less, after this we receive this log: Command GET for key ‘classTag::access_token’ failed. stack_trace: redis.actors.InvalidRedisReply$: Could not decode the redis reply (Connection closed)\n\tat redis.actors.InvalidRedisReply$.<clinit>(RedisReplyDecoder.scala)\n\tat redis.actors.RedisReplyDecoder$$anonfun$postStop$1.apply(RedisReplyDecoder.scala:20)\n\tat redis.actors.RedisReplyDecoder$$anonfun$postStop$1.apply(RedisReplyDecoder.scala:19)\n\tat scala.collection.LinearSeqOptimized$class.foreach(LinearSeqOptimized.scala:73)\n\tat scala.collection.mutable.MutableList.foreach(MutableList.scala:30)\n\tat redis.actors.RedisReplyDecoder.postStop(RedisReplyDecoder.scala:19)\n\tat akka.actor.Actor$class.aroundPostStop(Actor.scala:527)\n\tat redis.actors.RedisReplyDecoder.aroundPostStop(RedisReplyDecoder.scala:11)\n\tat akka.actor.dungeon.FaultHandling$class.akka$actor$dungeon$FaultHandling$$finishTerminate(FaultHandling.scala:210)\n\tat akka.actor.dungeon.FaultHandling$class.terminate(FaultHandling.scala:172)\n\tat akka.actor.ActorCell.terminate(ActorCell.scala:370)\n\tat akka.actor.ActorCell.invokeAll$1(ActorCell.scala:468)\n\tat akka.actor.ActorCell.systemInvoke(ActorCell.scala:484)\n\tat akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:282)\n\tat akka.dispatch.Mailbox.processMailbox(Mailbox.scala:260)\n\tat akka.dispatch.Mailbox.run(Mailbox.scala:224)\n\tat akka.dispatch.Mailbox.exec(Mailbox.scala:234)\n\tat akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)\n\tat akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)\n\tat akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)\n\tat akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)\n

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:18 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
mmolinoscommented, Nov 24, 2017

I discovered that is problem with my local configuration of docker thanks for all help

0reactions
mmolinoscommented, Nov 24, 2017

Hi Karel,

I update my code with this error that you comment and I have the same error. Can you reproduce it with my new code? https://github.com/mmolinos/examplePlayRedisPlayConnector

[info] play.api.Play - Application started (Dev)
[warn] r.a.RedisClientActor - ConnectionClosed ErrorClosed(Reset connection by the remote machine)
[error] p.a.cache.redis - Command GET for key 'classTag::CACHE_KEY' failed.
redis.actors.InvalidRedisReply$: Could not decode the redis reply (Connection closed)
	at redis.actors.InvalidRedisReply$.<clinit>(RedisReplyDecoder.scala)
	at redis.actors.RedisReplyDecoder.$anonfun$postStop$1(RedisReplyDecoder.scala:20)
	at scala.collection.LinearSeqOptimized.foreach(LinearSeqOptimized.scala:71)
	at scala.collection.LinearSeqOptimized.foreach$(LinearSeqOptimized.scala:68)
	at scala.collection.mutable.MutableList.foreach(MutableList.scala:30)
	at redis.actors.RedisReplyDecoder.postStop(RedisReplyDecoder.scala:19)
	at akka.actor.Actor.aroundPostStop(Actor.scala:536)
	at akka.actor.Actor.aroundPostStop$(Actor.scala:536)
	at redis.actors.RedisReplyDecoder.aroundPostStop(RedisReplyDecoder.scala:11)
	at akka.actor.dungeon.FaultHandling.finishTerminate(FaultHandling.scala:210)
Read more comments on GitHub >

github_iconTop Results From Across the Web

Could not connect to redis connection refused - Fix it easily
The most common reason for the connection refused error is that the Redis-Server is not started. Redis server should be started to use...
Read more >
Troubleshooting Redis
We have a long history of users experiencing crashes with Redis that actually turned out to be servers with broken RAM. Please test...
Read more >
Redis connection to 127.0.0.1:6379 failed - Stack Overflow
I solve this problem in next way: sudo apt-get install redis-server. then run command to confirm that everything ok:
Read more >
Troubleshoot connecting to an ElastiCache for Redis cluster
The most common issues are: The cluster isn't ready. The cluster is unhealthy. The network configuration is incorrect. The client configuration ...
Read more >
Redis Connection Issues - Heroku Help
Your app is no longer connecting to Redis and you are seeing errors relating to the self signed certificate. Eg: <OpenSSL::SSL::SSLError: SSL_connect returned=1 ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found