Chris Peake
Results
3
comments of
Chris Peake
I am also getting this exact error message running the same sample code, has this been investigated any further?
Confirmed that there is a bug in the 0.5.0 build by running the same sample code against the latest JOhm source code compiled locally which works.
There is also an incompatibility in the JOhm class itself against Jedis 2.0.0 because JedisException has been moved into redis.clients.jedis.exceptions.JedisException.