1

我们有一个来自播放框架应用程序的 redis 客户端调用。这个 Redis 调用是由使用 Akka Schedular 的 Actor 进行的。该调度程序每 60 秒运行一次，它会与其他 JDBC 调用一起进行 redis 调用。调度程序运行几分钟后，我们开始看到日志文件出现以下情况，并且应用程序停止响应任何 Redis 客户端调用。这是我第一次遇到 Redis，所以任何指针，帮助表示赞赏。

redis.host = localhost

redis.port = 6379

redis.timeout = 10

redis.pool.maxActive =110

redis.pool.maxIdle = 50

redis.pool.maxWait = 3000

redis.pool.testOnBorrow = true

redis.pool.testOnReturn = true

redis.pool.testWhileIdle = true

redis.pool.timeBetweenEvictionRunsMillis = 60000

redis.pool.numTestsPerEvictionRun = 10

Exception details:

redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketException: Broken pipe
    at redis.clients.jedis.Connection.flush(Connection.java:69) ~[redis.clients.jedis-2.3.0.jar:na]
    at redis.clients.jedis.JedisPubSub.subscribe(JedisPubSub.java:58) ~[redis.clients.jedis-2.3.0.jar:na]
............    
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:498) [com.typesafe.akka.akka-actor_2.10-2.2.0.jar:2.2.0]
    at akka.actor.ActorCell.invoke(ActorCell.scala:456) [com.typesafe.akka.akka-actor_2.10-2.2.0.jar:2.2.0]
    at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:237) [com.typesafe.akka.akka-actor_2.10-2.2.0.jar:2.2.0]
    at akka.dispatch.Mailbox.run(Mailbox.scala:219) [com.typesafe.akka.akka-actor_2.10-2.2.0.jar:2.2.0]
    at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:386) [com.typesafe.akka.akka-actor_2.10-2.2.0.jar:2.2.0]
    at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) [org.scala-lang.scala-library-2.10.3.jar:na]
    at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) [org.scala-lang.scala-library-2.10.3.jar:na]
    at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) [org.scala-lang.scala-library-2.10.3.jar:na]
    at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) [org.scala-lang.scala-library-2.10.3.jar:na]
Caused by: java.net.SocketException: Broken pipe
    at java.net.SocketOutputStream.socketWrite0(Native Method) ~[na:1.7.0_51]
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) ~[na:1.7.0_51]
    at java.net.SocketOutputStream.write(SocketOutputStream.java:159) ~[na:1.7.0_51]
    at redis.clients.util.RedisOutputStream.flushBuffer(RedisOutputStream.java:31) ~[redis.clients.jedis-2.3.0.jar:na]
    at redis.clients.util.RedisOutputStream.flush(RedisOutputStream.java:223) ~[redis.clients.jedis-2.3.0.jar:na]
    at redis.clients.jedis.Connection.flush(Connection.java:67) ~[redis.clients.jedis-2.3.0.jar:na]
    ... 15 common frames omitted
4

2 回答 2

0

我最近在使用 Redis 时遇到了类似的问题，问题是，我在订阅后没有返回 Jedis 资源，因此连接泄漏，并且在几次连接后应用程序没有响应。因此，无论您做什么，都不要忘记返回绝地资源：

Jedis j = play.Play.application().plugin(RedisPlugin.class).jedisPool().getResource();
j.subscribe(listener, redisChannel);
play.Play.application().plugin(RedisPlugin.class).jedisPool().returnResource(j);
于 2014-03-07T22:12:32.287 回答
0

问题在于超时，并且您用来进行订阅的客户端超时/获得了 DC 编辑。

于 2014-03-06T12:53:34.373 回答