Jedis.hmset() has thrown a JedisDataException

redis.clients.jedis.exceptions.JedisDataException
Javadoc
at redis.clients.jedis.Protocol.processError
(source)
at redis.clients.jedis.Protocol.process
(source)
at redis.clients.jedis.Protocol.read
(source)
at redis.clients.jedis.Connection.readProtocolWithCheckingBroken
(source)
at redis.clients.jedis.Connection.getStatusCodeReply
(source)
at redis.clients.jedis.Jedis.hmset
(source)
5 frames hidden

Typical Exception Messages

  1. ERR wrong number of arguments for 'hmset' command
  2. OOM command not allowed when used memory > 'maxmemory'.
  3. MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

Origin

Cannot read Redis response as status code since Redis returned an unknown error code

redis.clients.jedis.exceptions.JedisDataException
4 frames hidden
redis.clients.jedis.Connection.getStatusCodeReply
28Web pages

Similar

External results for this pattern (2)

  1. kaiwu1121via GitHub1 month ago
    MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
    Show stack trace
  2. v11via Stack Overflow4 months ago
    OOM command not allowed when used memory > 'maxmemory'.
    Show stack trace