Java連接redis報錯timed?out問題的解決辦法
現(xiàn)象
- 之前寫了一篇文章:Spring redis使用報錯Read timed out排查解決,解決超時問題
- 后面發(fā)現(xiàn)解決的不徹底,仍有報錯
- 詳細查看了下源碼,發(fā)現(xiàn)不同版本里,參數(shù)名不一樣,之前的參數(shù)設置,并沒有在新版本里生效
報錯一
- 核心報錯提示是這一句:
JedisConnectionException: java.net.SocketTimeoutException: Read timed out
- 使用jedis連接時,連接超時
SocketTimeout
,即與Redis服務器的連接超時
2023-03-29 10:54:38.186 ERROR 9136 --- [ntainer#7-0-C-1] c.n.r.service.IntersectionQueryService : Exception in getIntersectionById() with cause = 'redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out' and exception = 'java.net.SocketTimeoutException: Read timed out; nested exception is redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out' org.springframework.data.redis.RedisConnectionFailureException: java.net.SocketTimeoutException: Read timed out; nested exception is redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out at org.springframework.data.redis.connection.jedis.JedisExceptionConverter.convert(JedisExceptionConverter.java:65) at org.springframework.data.redis.connection.jedis.JedisExceptionConverter.convert(JedisExceptionConverter.java:42) at org.springframework.data.redis.PassThroughExceptionTranslationStrategy.translate(PassThroughExceptionTranslationStrategy.java:44) at org.springframework.data.redis.FallbackExceptionTranslationStrategy.translate(FallbackExceptionTranslationStrategy.java:42) at org.springframework.data.redis.connection.jedis.JedisConnection.convertJedisAccessException(JedisConnection.java:187) at org.springframework.data.redis.connection.jedis.JedisConnection.doWithJedis(JedisConnection.java:802) at org.springframework.data.redis.connection.jedis.JedisConnection.doInvoke(JedisConnection.java:160) at org.springframework.data.redis.connection.jedis.JedisConnection.lambda$new$0(JedisConnection.java:69) at org.springframework.data.redis.connection.jedis.JedisInvoker$Synchronizer.invoke(JedisInvoker.java:1027) at org.springframework.data.redis.connection.jedis.JedisInvoker$DefaultSingleInvocationSpec.getOrElse(JedisInvoker.java:946) at org.springframework.data.redis.connection.jedis.JedisStringCommands.setEx(JedisStringCommands.java:176) at org.springframework.data.redis.connection.DefaultedRedisConnection.setEx(DefaultedRedisConnection.java:334) at org.springframework.data.redis.connection.DefaultStringRedisConnection.setEx(DefaultStringRedisConnection.java:1138) at org.springframework.data.redis.core.DefaultValueOperations$8.potentiallyUsePsetEx(DefaultValueOperations.java:337) at org.springframework.data.redis.core.DefaultValueOperations$8.doInRedis(DefaultValueOperations.java:330) at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:223) at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:190) at org.springframework.data.redis.core.AbstractOperations.execute(AbstractOperations.java:97) at org.springframework.data.redis.core.DefaultValueOperations.set(DefaultValueOperations.java:325) at com.newatc.radar.service.IntersectionQueryService.getAllIntersections(IntersectionQueryService.java:70)
報錯二
- 核心報錯提示是這一句:
Error while validating pooled Jedis object
- 連接池內(nèi)的Jedis對象已經(jīng)失效或已經(jīng)關(guān)閉,沒有可用的jedis客戶端
2023-08-24 09:44:23.721 ERROR 92250 --- [ns-pool-evictor] redis.clients.jedis.JedisFactory : Error while validating pooled Jedis object. redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out at redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:205) at redis.clients.jedis.util.RedisInputStream.readByte(RedisInputStream.java:43) at redis.clients.jedis.Protocol.process(Protocol.java:162) at redis.clients.jedis.Protocol.read(Protocol.java:227) at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352) at redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:270) at redis.clients.jedis.BinaryJedis.ping(BinaryJedis.java:380) at redis.clients.jedis.JedisFactory.validateObject(JedisFactory.java:214) at org.apache.commons.pool2.impl.GenericObjectPool.evict(GenericObjectPool.java:745) at org.apache.commons.pool2.impl.BaseGenericObjectPool$Evictor.run(BaseGenericObjectPool.java:160) at org.apache.commons.pool2.impl.EvictionTimer$WeakRunner.run(EvictionTimer.java:113) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.net.SocketTimeoutException: Read timed out at java.base/java.net.SocketInputStream.socketRead0(Native Method) at java.base/java.net.SocketInputStream.socketRead(SocketInputStream.java:115) at java.base/java.net.SocketInputStream.read(SocketInputStream.java:168) at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140) at java.base/java.net.SocketInputStream.read(SocketInputStream.java:126) at redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:199) ... 16 common frames omitted 2023-08-24 09:44:25.724 ERROR 92250 --- [ns-pool-evictor] redis.clients.jedis.JedisFactory : Error while validating pooled Jedis object. redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out at redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:205) at redis.clients.jedis.util.RedisInputStream.readByte(RedisInputStream.java:43) at redis.clients.jedis.Protocol.process(Protocol.java:162) at redis.clients.jedis.Protocol.read(Protocol.java:227) at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352) at redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:270) at redis.clients.jedis.BinaryJedis.ping(BinaryJedis.java:380) at redis.clients.jedis.JedisFactory.validateObject(JedisFactory.java:214) at org.apache.commons.pool2.impl.GenericObjectPool.evict(GenericObjectPool.java:745) at org.apache.commons.pool2.impl.BaseGenericObjectPool$Evictor.run(BaseGenericObjectPool.java:160) at org.apache.commons.pool2.impl.EvictionTimer$WeakRunner.run(EvictionTimer.java:113) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.net.SocketTimeoutException: Read timed out at java.base/java.net.SocketInputStream.socketRead0(Native Method) at java.base/java.net.SocketInputStream.socketRead(SocketInputStream.java:115) at java.base/java.net.SocketInputStream.read(SocketInputStream.java:168) at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140) at java.base/java.net.SocketInputStream.read(SocketInputStream.java:126) at redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:199) ... 16 common frames omitted
解決
- 報錯是發(fā)生在我們的環(huán)境,事實上,我們的平臺并沒有那么高的并發(fā)量,只有一些造數(shù)據(jù)腳本在跑和調(diào)用redis
- 而且所有應用服務和redis服務,都在一個內(nèi)網(wǎng)環(huán)境里,不應該有網(wǎng)絡波動的問題,但發(fā)生這個報錯時,使用可視化工具連接redis,可以發(fā)現(xiàn),Redis服務是正常的
- 最終發(fā)現(xiàn),是我們沒有針對新版本,配置好超時參數(shù)
- 原有配置
spring: redis: host: 192.168.1.50 port: 6379 password: database: 0 jedis: pool: min-idle: 10 max-idle: 400 max-wait: 30000 max-active: 200
- 查看了源碼后發(fā)現(xiàn),少了對于redis客戶端連接維護的超時時間設置,這個超時時間默認是2s,有時候是不夠用的
- 當大并發(fā)量來臨,或者大量對象存儲更新時,阻塞可能會超過2s時,就會報錯
SocketTimeoutException
- 新的配置(時間可以寫毫秒,也可以帶單位)
spring.redis.timeout
:是指與redis服務器的讀寫超時時間,讀寫操作時會判斷這個spring.redis.connect-timeout
:是指與redis服務器的連接超時時間,默認2s,這個可以設置大一點,例如30s,保證短時的網(wǎng)絡波動不影響連接spring.redis.jedis.pool.min-idle
:最小空閑連接,可以根據(jù)需要寫,我這里設置為8spring.redis.jedis.pool.max-idle
:最大空閑連接,可以根據(jù)需要寫,我這里設置為200,夠用了spring.redis.jedis.pool.max-wait
:連接池最大阻塞等待時間(使用負值表示沒有限制),這個是指服務從連接池獲取連接的等待時間,我這里設置為30s,夠用了spring.redis.jedis.pool.max-active
:連接池最大連接數(shù)(使用負值表示沒有限制),根據(jù)我們的應用數(shù)量設置,我這里設置256,足夠用了
spring: redis: host: 192.168.1.50 port: 6379 password: database: 0 timeout: 30s # 讀寫超時 connect-timeout: 60s #連接超時 jedis: pool: min-idle: 8 # 最小空閑連接 max-idle: 200 # 最大空閑連接 max-wait: 30s # 連接池最大阻塞等待時間(使用負值表示沒有限制) max-active: 256 # 連接池最大連接數(shù)(使用負值表示沒有限制)
- 總結(jié)一下,一開始只配置了參數(shù)
spring.redis.jedis.pool.max-wait
連接池最大阻塞等待時間,而沒有配置spring.redis.timeout
和spring.redis.connect-timeout
,導致偶發(fā)的超時 - 配置上這兩個參數(shù)后,就沒有遇到超時報錯了
- 最后再介紹下Jedis連接池吧
Jedis連接池
Jedis連接池是用于管理Jedis客戶端連接的一種機制。Jedis是一個非常流行的Java Redis客戶端,它允許Java開發(fā)人員與Redis服務器進行交互。
Jedis連接池的目的是為了提高應用程序與Redis服務器之間的性能和可擴展性。通過連接池,應用程序可以重復利用現(xiàn)有的連接而不是創(chuàng)建新的連接,從而減少連接的創(chuàng)建和銷毀的開銷。
Jedis連接池的實現(xiàn)中有幾個主要的組件:
連接池配置(Config):用于設置連接池的參數(shù),如最大連接數(shù)、最大空閑連接數(shù)、連接超時時間等。
連接池對象(JedisPool):用于創(chuàng)建和管理Jedis連接。
Jedis連接(Jedis):用于與Redis服務器進行交互的對象。
連接池的工作原理如下:
- 初始化:當連接池被創(chuàng)建時,它會根據(jù)配置參數(shù)建立一定數(shù)量的連接,并放入連接池中。
- 借用連接:當應用程序需要與Redis服務器進行交互時,它可以從連接池中獲取一個空閑連接。
- 使用連接:應用程序使用連接進行操作,如執(zhí)行命令、讀寫數(shù)據(jù)等操作。
- 歸還連接:應用程序完成操作后,將連接歸還給連接池,以便其他線程或請求可以繼續(xù)使用該連接。
- 連接池管理:連接池會根據(jù)預設的策略來管理連接的狀態(tài),如連接的獲取、釋放、逐出等。
使用Jedis連接池可以提高應用程序與Redis服務器之間的性能和資源利用率。通過合理配置連接池的參數(shù),可以控制連接數(shù)、連接超時時間、最大空閑連接數(shù)等,以適應不同規(guī)模的應用程序需求。同時,連接池還可以提供連接的可用性檢查、自動重連、連接匯報等功能,提高應用的可靠性和穩(wěn)定性。
總結(jié)
到此這篇關(guān)于Java連接redis報錯timed out問題解決的文章就介紹到這了,更多相關(guān)Java連接redis報錯timed out內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!

Java基于面向?qū)ο髮崿F(xiàn)一個戰(zhàn)士小游戲

使用springboot打包成zip部署,并實現(xiàn)優(yōu)雅停機