It seems like server has closed the connection about jedis HOT 6 CLOSED

Jedis: 1.5.0
Redis: redis-2.2.0-rc2.tar.gz

from jedis.

You need to configure the pool with "testOnBorrow = true" ...
Redis server is shuting down the connections after a while, and you need to test if the connection is still useable on the client side ...

from jedis.

Thank you it works!

from jedis.

Just to beat a dead horse a bit, might a good pool setup for a long running server process be as simple as:

JedisPoolConfig config = new JedisPoolConfig();
config.setTestOnBorrow(true);
this.pool = new JedisPool(config, this.redisServer, this.redisPort);

from jedis.

when i use redis-2.2.2 and jedis-1.5.2

static {
if (pool == null) {
redis.clients.jedis.JedisPoolConfig config = new redis.clients.jedis.JedisPoolConfig();
config.maxActive = 20;
config.maxIdle = 10;
config.maxWait = 1000;
config.testOnBorrow = true;
pool = new JedisPool(config, REDISHOST, REDISPORT);
}
}

i got the following and do not know why，~~~~(>_<)~~~~ :

redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool

java.util.NoSuchElementException: Could not create a validated object, cause: ValidateObject failed org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1203)
redis.clients.util.Pool.getResource(Pool.java:20)

from jedis.

jedis with some error： when redis server send back "Protocol error" message , the server will close socket; but jedis Protocol.java just throw a JedisDataException exception and ignored tcp close segment; so if you reuse this connection, jedis will throw an exception with "It seems like server has closed the connection" message.

from jedis.