org.redisson.client.RedisTimeoutException: Redis server response timeout (3000 ms) occured for command: (PUBLISH) with params: [dispatch_except, com.corundumstudio.socketio.store.pubsub.DispatchMessage@11dd736] channel: [id: 0xd8161b77, L:/10.1.5.114:9741 - R:10.1.6.20/10.1.6.20:7091]

GitHub | pengfei-xu | 9 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

    pub/sub timeout

    GitHub | 9 months ago | pengfei-xu
    org.redisson.client.RedisTimeoutException: Redis server response timeout (3000 ms) occured for command: (PUBLISH) with params: [dispatch_except, com.corundumstudio.socketio.store.pubsub.DispatchMessage@11dd736] channel: [id: 0xd8161b77, L:/10.1.5.114:9741 - R:10.1.6.20/10.1.6.20:7091]
  2. 0

    GitHub comment 541#231044874

    GitHub | 9 months ago | Mavlarn
    org.redisson.client.RedisTimeoutException: Redis server response timeout (15000 ms) occured for command: (EVAL) with params: [if (redis.call('exists', KEYS[1]) == 0) then redis.call('hset', KEYS[1], ARGV[2], 1); redis.call('pexpire', KEYS[1], ARGV[1]); return nil; end; if (redis.call('hexists', KEYS[1], ARGV[2]) == 1) then redis.call('hincrby', KEYS[1], ARGV[2], 1); redis.call('pexpire', KEYS[1], ARGV[1]); return nil; end; return redis.call('pttl', KEYS[1]);, 1, ticket.lock.master_slave, 70000, 623be78d-901f-4b99-9580-3dcc9ca7b860:40] channel: [id: 0xfca13790, L:/127.0.0.1:37426 - R:/127.0.0.1:6379]
  3. 0

    Configured Timeout in ElasticCacheServerConfig being ignored

    GitHub | 5 months ago | tankchintan
    org.redisson.client.RedisTimeoutException: Redis server response timeout (1000 ms) occured for command: (GET) with params: [XXXXX] channel: [id: 0x002202e0, L:/172.17.0.160:43221 - R://XXX.002.cache.amazonaws.com/10.169.226.201:6379]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    org.redisson.client.RedisTimeoutException

    GitHub | 2 months ago | koywang
    org.redisson.client.RedisTimeoutException: Redis server response timeout (3000 ms) occured for command: (SET) with params: [hello_109579, 109579] channel: [id: 0x96dcff25, L:/192.168.9.225:50421 - R:/192.168.9.125:7503]
  6. 0

    GitHub comment 744#271464922

    GitHub | 2 months ago | koywang
    org.redisson.client.RedisTimeoutException: Redis server response timeout (3000 ms) occured for command: (EVAL) with params: [local v = redis.call('hget', KEYS[1], ARGV[1]); redis.call('hset', KEYS[1], ARGV[1], ARGV[2]); retur..., 1, map_7, key_62727, value_62727] channel: [id: 0x8a13f814, L:/192.168.9.225:49464 - R:/192.168.9.125:6379]

    2 unregistered visitors

    Root Cause Analysis

    1. org.redisson.client.RedisTimeoutException

      Redis server response timeout (3000 ms) occured for command: (PUBLISH) with params: [dispatch_except, com.corundumstudio.socketio.store.pubsub.DispatchMessage@11dd736] channel: [id: 0xd8161b77, L:/10.1.5.114:9741 - R:10.1.6.20/10.1.6.20:7091]

      at org.redisson.command.CommandAsyncService$10.run()
    2. org.redisson.command
      CommandAsyncService$10.run
      1. org.redisson.command.CommandAsyncService$10.run(CommandAsyncService.java:510)[redisson-2.2.17-SNAPSHOT.jar:na]
      1 frame
    3. Netty
      HashedWheelTimer$Worker.run
      1. io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:581)[netty-common-4.1.0.Final.jar:4.1.0.Final]
      2. io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:655)[netty-common-4.1.0.Final.jar:4.1.0.Final]
      3. io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:367)[netty-common-4.1.0.Final.jar:4.1.0.Final]
      3 frames
    4. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:745)[na:1.7.0_65]
      1 frame