You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while enable event publisher but no LATENCY_UTILS_AVAILABLE or HDR_UTILS_AVAILABLE, the connection will be failed and throw Exception:
Caused by: io.lettuce.core.RedisConnectionException: Unable to connect to localhost/<unresolved>:6379
at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78)
at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56)
at io.lettuce.core.AbstractRedisClient.getConnection(AbstractRedisClient.java:330)
at io.lettuce.core.RedisClient.connect(RedisClient.java:216)
at org.springframework.data.redis.connection.lettuce.StandaloneConnectionProvider.lambda$getConnection$1(StandaloneConnectionProvider.java:115)
at java.base/java.util.Optional.orElseGet(Optional.java:362)
at org.springframework.data.redis.connection.lettuce.StandaloneConnectionProvider.getConnection(StandaloneConnectionProvider.java:115)
at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory$ExceptionTranslatingConnectionProvider.getConnection(LettuceConnectionFactory.java:1459)
... 77 more
Caused by: java.lang.ClassCastException: class io.lettuce.core.metrics.DefaultCommandLatencyCollector$PauseDetectorWrapper$1 cannot be cast to class io.lettuce.core.metrics.DefaultCommandLatencyCollector$DefaultPauseDetectorWrapper (io.lettuce.core.metrics.DefaultCommandLatencyCollector$PauseDetectorWrapper$1 and io.lettuce.core.metrics.DefaultCommandLatencyCollector$DefaultPauseDetectorWrapper are in unnamed module of loader 'app')
at io.lettuce.core.metrics.DefaultCommandLatencyCollector.recordCommandLatency(DefaultCommandLatencyCollector.java:108)
at io.lettuce.core.protocol.CommandHandler.recordLatency(CommandHandler.java:914)
at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:770)
at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:658)
at io.lettuce.core.protocol.CommandHandler.channelRead(CommandHandler.java:598)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:832)
The text was updated successfully, but these errors were encountered:
HashJang
added a commit
to HashJang/lettuce-core
that referenced
this issue
Aug 21, 2021
mp911de
changed the title
Connect failed while no LATENCY_UTILS_AVAILABLE or HDR_UTILS_AVAILABLEClassCastException when no LATENCY_UTILS_AVAILABLE or HDR_UTILS_AVAILABLEAug 25, 2021
while enable event publisher but no LATENCY_UTILS_AVAILABLE or HDR_UTILS_AVAILABLE, the connection will be failed and throw Exception:
The text was updated successfully, but these errors were encountered: