Just defining a redis bean using Jredis sends all of my cpu's to 100%

[slyfox]

I have commented out every actual redis action in my code and the cpu still hits 100% which I assume to mean that it is something with the Jedis lib or config. I have checked the Jedis google group and there are stories of hitting 100% cpu but with much different causes.

Anyone had any similar problems? Not really sure where to start on this one.

[Costin Leau]

Hasn't happened to me so I don't know what to tell you - try connecting to the JVM and see what thread eats the CPU. It's probably some sort of loop - try commenting out Jedis as well as see whether it helps. Also try the other libraries in Spring Data Redis to see whether they alleviate the problem.