通过Jedis客户端连接不到redis

ゝ一纸荒年。 2022-09-25 02:20 254阅读 0赞

当我使用如下的代码来测试redis的时候报错,代码如下:

  1. // 单机版测试
  2. @Test
  3. public void testJedisSingle() throws Exception {
  4. Jedis jedis = new Jedis("192.168.1.118", 6379);
  5. jedis.set("shenlinnan", "hahahahahaha");
  6. System.out.println(jedis.get("shenlinnan"));
  7. jedis.close();
  8. }

报错信息如下:

  1. redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: connect timed out
  2. at redis.clients.jedis.Connection.connect(Connection.java:207)
  3. at redis.clients.jedis.BinaryClient.connect(BinaryClient.java:93)
  4. at redis.clients.jedis.Connection.sendCommand(Connection.java:126)
  5. at redis.clients.jedis.BinaryClient.set(BinaryClient.java:110)
  6. at redis.clients.jedis.Client.set(Client.java:47)
  7. at redis.clients.jedis.Jedis.set(Jedis.java:120)
  8. at com.juhehl.kapu.rest.component.impl.JedisClientSingleTest.testJedisSingle(JedisClientSingleTest.java:24)
  9. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  10. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  11. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  12. at java.lang.reflect.Method.invoke(Method.java:497)
  13. at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
  14. at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
  15. at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
  16. at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
  17. at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
  18. at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
  19. at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
  20. at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
  21. at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
  22. at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
  23. at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
  24. at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
  25. at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
  26. at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
  27. at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
  28. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
  29. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
  30. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
  31. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
  32. Caused by: java.net.SocketTimeoutException: connect timed out
  33. at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
  34. at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
  35. at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
  36. at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
  37. at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
  38. at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
  39. at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
  40. at java.net.Socket.connect(Socket.java:589)
  41. at redis.clients.jedis.Connection.connect(Connection.java:184)
  42. ... 29 more

很明显,我无法连接到我刚刚安装的redis上,这时候使用windows的telnet命令,猜测是由于linux的防火墙导致的无法连接到redis,所以,先查看一下防火墙的位置,如图所示:

Center

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

Center 1

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

SouthEast

结果显示操作redis正常,可以得出结论,就是linux的防火墙影响的redis的连接,所以,我要重新开启防火墙,在开启之后,增加这个端口号可以外网访问,首先,先进行开启防火墙的操作,如图:

20160805105210417

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

20160805105316752

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

20160805105448676

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

20160805105559474

再次进行程序测试,如图:

20160805110604535

结果正确,这样就可以正常的访问redis了。

发表评论

表情:
评论列表 (有 0 条评论,254人围观)

还没有评论,来说两句吧...

相关阅读

    相关 Redis 客户Jedis 事务

    Redis 事务可以一次执行多个命令, 并且带有以下两个重要的保证: 1.事务是一个单独的隔离操作:事务中的所有命令都会序列化、按顺序地执行。事务在执行的过程中,不会被其他