redis.clients.jedis.exceptions.JedisDataException

NOSCRIPT No matching script. Please use EVAL.

Samebug tips3

Redis has some limitations of various bulk length, the length of args of the API command MSET can't be bigger than 1024*1024, set a limiter on how big your list is to avoid this.

You're experiencing issue #124 in spring session: https://goo.gl/CgfzZ2. You can use the workaround described here: https://goo.gl/pnn7Cc or check the bug page mentioned for disscussion about it!

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web28

  • NOSCRIPT No matching script. Please use EVAL.
  • via GitHub by xetorthio
    , 11 months ago
    NOSCRIPT No matching script. Please use EVAL.
  • via Spring JIRA by Jennifer Hickey, 1 year ago
    Cannot use Jedis when in Multi. Please use JedisTransaction instead.
  • Stack trace

    • redis.clients.jedis.exceptions.JedisDataException: NOSCRIPT No matching script. Please use EVAL. at redis.clients.jedis.Protocol.processError(Protocol.java:115) at redis.clients.jedis.Protocol.process(Protocol.java:141) at redis.clients.jedis.Protocol.read(Protocol.java:196) at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:283) at redis.clients.jedis.Connection.getOne(Connection.java:265) at redis.clients.jedis.Connection.getOne(Connection.java:265) at redis.clients.jedis.Jedis.getEvalResult(Jedis.java:2907) at redis.clients.jedis.Jedis.evalsha(Jedis.java:2934) at redis.clients.jedis.custom.Jedis.evalsha(Jedis.java:57)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 11 months ago
    3676 times, 11 months ago
    Unknown user
    Once, 1 year ago
    29 more bugmates