Problem:

I am getting junk values like "OK" for redis get call. This issue reproduces often over a particular period of time irrespective of the keys trying to obtain through get command.

I'm Using :

Redis version 2.8 Jedis client 2.5.1 to connect Redis

Comment From: michael-grunder

This is most likely a problem with the library, not Redis itself.

Comment From: mgravell

Getting the wrong type of response would usually - in the case of client libraries - indicate something like a threading bug. I'm not familiar enough with Jedis to know what the expected threading model is, but the first thing I would check is: are you sharing a connection between multiple threads when Jedis is not expecting you to? Some clients expect and allow for concurrency; some enforce single-threaded access in the library, and some expect the caller to deal with that. On 25 Jan 2016 3:14 p.m., "rajasuba" notifications@github.com wrote:

Problem:

I am getting junk values like "OK" for redis get call This issue reproduces often over a particular period of time irrespective of the keys trying to obtain through get command

I'm Using :

Redis version 28 Jedis client 251 to connect Redis

— Reply to this email directly or view it on GitHub https://github.com/antirez/redis/issues/3032.

Comment From: filipecosta90

Closing this issue given there is no reason to believe this is a redis issue. As a follow-up, if this issue is still happening please do share it on https://github.com/redis/jedis.