欢迎您访问程序员文章站本站旨在为大家提供分享程序员计算机编程知识!
您现在的位置是: 首页

Jedis连接失败 Could not get a resource from the pool] with root cause

程序员文章站 2022-05-18 09:33:15
...

网上差了很多例子,都是说连接池个数问题,或者是超时问题,但是始终并没有解决问题。

后来看了一片文章,提到有可能是linux防火墙问题造成的,果断测试一下

所以,先查看一下防火墙的位置,如图所示:

Jedis连接失败 Could not get a resource from the pool] with root cause

以前都是用iptables,但是centos7.0之后就换成了firewalled了,那么我查看了firewalled的状态为active(running),很明显是在运行中的了,我尝试关闭一下防火墙,看看是不是防火墙影响的我无法访问redis,如图:

Jedis连接失败 Could not get a resource from the pool] with root cause

关闭之后,测试一下程序,如图:

Exception in thread "main" redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions:
 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent.
 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server
 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 
 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.
    at redis.clients.jedis.Protocol.processError(Protocol.java:127)
    at redis.clients.jedis.Protocol.process(Protocol.java:161)
    at redis.clients.jedis.Protocol.read(Protocol.java:215)
    at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
    at redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:239)
    at redis.clients.jedis.BinaryJedis.ping(BinaryJedis.java:196)
    at com.example.redis.JedisTest.main(JedisTest.java:24)

结果又报错,我的天啊,不过仔细看看发现它提供了4个解决方案,所以至少可以得出结论,就是linux的防火墙影响的redis的连接,所以,我要重新开启防火墙,在开启之后,增加这个端口号可以外网访问,首先,先进行开启防火墙的操作,如图:

Jedis连接失败 Could not get a resource from the pool] with root cause

再次检查一下防火墙的状态,如图:

Jedis连接失败 Could not get a resource from the pool] with root cause

这样说明已经正常开启了防火墙,下面需要开启6379端口,如图:

Jedis连接失败 Could not get a resource from the pool] with root cause

success说明添加成功了,下面需要重新启动防火墙,如图:

Jedis连接失败 Could not get a resource from the pool] with root cause

防火墙的问题解决了,之后就是看看在这4个解决方案中去哪一种方案了。

1.修改redis.conf配置文件,将绑定的ip地址端口号给注释见下图 
  Jedis连接失败 Could not get a resource from the pool] with root cause

  2.由于Linux上的redis处于安全保护模式,这就让你无法从虚拟机外部去轻松建立连接,这里就有两种解决方法,一种是在redis.conf中设置保护模式为no,见下图 
  Jedis连接失败 Could not get a resource from the pool] with root cause

  3.另外一种方式是加上安全认证,即redis默认是没有密码的可以直接登录,这里加上密码,配置见下图 
  Jedis连接失败 Could not get a resource from the pool] with root cause

  4.好吧,此时你以为轻松解决问题了,于是再次在Linux启动redis服务器后,在外部连接还是报错,真是too young too native,起初我以为是配置没有生效,因为明明配置都写好了,于是杀掉redis的相关进程重启服务,结果发现还是没卵用。最后研究发现问题所在:之前启动redis-server并没有指定配置文件,而Linux上的redis比较操蛋的一点就是如果你不指定配置文件去启动,那么你做的修改就没有用,会读取默认配置(PS:至于这个默认配置在哪我也不清楚),于是用下面这种方式启动就可以使修改的配置文件生效,至于config rewrite命令我测试了并没有什么卵用。 
  Jedis连接失败 Could not get a resource from the pool] with root cause

  5.再次测试,在windows上进行jedis连接测试,出现下面pong(),恼人的错误终于消失了,比起windows版本的redis还真是让人龟毛啊,如果配置了密码认证,调用Jedis的auth方法输入密码即可 



总结一下:

1.关闭LINUX上的防火墙

2.修改redis配置文件中的本地绑定(注释掉bind 127.0.0.1)

3.提供验证密码



相关标签: redis jedis