redis.clients.jedis.exceptions.JedisDataException: NOSCRIPT No matching script. Please use EVAL.

GitHub | xetorthio | 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

    GitHub comment 1259#239187988

    GitHub | 6 months ago | srirama-rayaprolu
    redis.clients.jedis.exceptions.JedisDataException: NOSCRIPT No matching script. Please use EVAL.
  2. 0

    GitHub comment 1259#239229780

    GitHub | 6 months ago | xetorthio
    redis.clients.jedis.exceptions.JedisDataException: NOSCRIPT No matching script. Please use EVAL.

    Root Cause Analysis

    1. redis.clients.jedis.exceptions.JedisDataException

      NOSCRIPT No matching script. Please use EVAL.

      at redis.clients.jedis.Protocol.processError()
    2. Jedis
      Jedis.evalsha
      1. redis.clients.jedis.Protocol.processError(Protocol.java:115)
      2. redis.clients.jedis.Protocol.process(Protocol.java:141)
      3. redis.clients.jedis.Protocol.read(Protocol.java:196)
      4. redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:283)
      5. redis.clients.jedis.Connection.getOne(Connection.java:265)
      6. redis.clients.jedis.Connection.getOne(Connection.java:265)
      7. redis.clients.jedis.Jedis.getEvalResult(Jedis.java:2907)
      8. redis.clients.jedis.Jedis.evalsha(Jedis.java:2934)
      8 frames
    3. redis.clients.jedis
      Jedis.evalsha
      1. redis.clients.jedis.custom.Jedis.evalsha(Jedis.java:57)
      1 frame