redisson的问题

最新推荐文章于 2024-05-19 16:20:18 发布
最新推荐文章于 2024-05-19 16:20:18 发布
阅读量1.2k 收藏
点赞数
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/jupiter_888/article/details/103852979
版权 

dc_app-web-22_1 | 2019-05-28T16:10:41.354016494Z 2019-05-29 00:10:41.353 logback [scheduling-1] ERROR o.s.s.s.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task.
dc_app-web-22_1 | 2019-05-28T16:10:41.354063961Z java.lang.ClassCastException: java.lang.Long cannot be cast to org.redisson.client.protocol.decoder.ListScanResult
dc_app-web-22_1 | 2019-05-28T16:10:41.354070357Z    at org.redisson.RedissonKeys$2.iterator(RedissonKeys.java:127)
dc_app-web-22_1 | 2019-05-28T16:10:41.354075209Z    at org.redisson.RedissonKeys$2.iterator(RedissonKeys.java:123)
dc_app-web-22_1 | 2019-05-28T16:10:41.354083179Z    at org.redisson.BaseIterator.hasNext(BaseIterator.java:54)
dc_app-web-22_1 | 2019-05-28T16:10:41.354087652Z    at org.redisson.misc.CompositeIterator.hasNext(CompositeIterator.java:39)
dc_app-web-22_1 | 2019-05-28T16:10:41.354091787Z    at java.lang.Iterable.forEach(Iterable.java:74)
dc_app-web-22_1 | 2019-05-28T16:10:41.354096102Z    at com.microfinance.market.app.biz.task.ScheduledEventTracking.getEventList(ScheduledEventTracking.java:144)
dc_app-web-22_1 | 2019-05-28T16:10:41.354100181Z    at com.microfinance.market.app.biz.task.ScheduledEventTracking.consumeChannelEvents(ScheduledEventTracking.java:124)
dc_app-web-22_1 | 2019-05-28T16:10:41.354104379Z    at com.microfinance.market.app.biz.task.ScheduledEventTracking.registerConsumeChannelEvents(ScheduledEventTracking.java:91)
dc_app-web-22_1 | 2019-05-28T16:10:41.354108064Z    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
dc_app-web-22_1 | 2019-05-28T16:10:41.354111585Z    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
dc_app-web-22_1 | 2019-05-28T16:10:41.354115049Z    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
dc_app-web-22_1 | 2019-05-28T16:10:41.354125963Z    at java.lang.reflect.Method.invoke(Method.java:498)
dc_app-web-22_1 | 2019-05-28T16:10:41.354128978Z    at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84)
dc_app-web-22_1 | 2019-05-28T16:10:41.354132248Z    at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
dc_app-web-22_1 | 2019-05-28T16:10:41.354134973Z    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
dc_app-web-22_1 | 2019-05-28T16:10:41.354137646Z    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
dc_app-web-22_1 | 2019-05-28T16:10:41.354140490Z    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
dc_app-web-22_1 | 2019-05-28T16:10:41.354145031Z    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
dc_app-web-22_1 | 2019-05-28T16:10:41.354149331Z    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
dc_app-web-22_1 | 2019-05-28T16:10:41.354153511Z    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
dc_app-web-22_1 | 2019-05-28T16:10:41.354157764Z    at java.lang.Thread.run(Thread.java:748)
dc_app-web-22_1 | 2019-05-28T16:10:41.354163953Z 2019-05-29 00:10:41.353 logback [redisson-netty-1-4] WARN  i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
dc_app-web-22_1 | 2019-05-28T16:10:41.354168922Z io.netty.handler.codec.DecoderException: CommandDecoder.decode() must consume the inbound data or change its state if it did not decode anything.
dc_app-web-22_1 | 2019-05-28T16:10:41.354172627Z    at io.netty.handler.codec.ReplayingDecoder.callDecode(ReplayingDecoder.java:379)
dc_app-web-22_1 | 2019-05-28T16:10:41.354175374Z    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278)
dc_app-web-22_1 | 2019-05-28T16:10:41.354178199Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-28T16:10:41.354180888Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-28T16:10:41.354183745Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-22_1 | 2019-05-28T16:10:41.354186570Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-22_1 | 2019-05-28T16:10:41.354189642Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-28T16:10:41.354192304Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-28T16:10:41.354195105Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-22_1 | 2019-05-28T16:10:41.354198081Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-22_1 | 2019-05-28T16:10:41.354200866Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-28T16:10:41.354207408Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-28T16:10:41.354210231Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-22_1 | 2019-05-28T16:10:41.354212986Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-22_1 | 2019-05-28T16:10:41.354215693Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-28T16:10:41.354218471Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-28T16:10:41.354221814Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-22_1 | 2019-05-28T16:10:41.354224642Z    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
dc_app-web-22_1 | 2019-05-28T16:10:41.354228090Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-28T16:10:41.354232509Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-28T16:10:41.354236405Z    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
dc_app-web-22_1 | 2019-05-28T16:10:41.354240450Z    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
dc_app-web-22_1 | 2019-05-28T16:10:41.354244681Z    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:648)
dc_app-web-22_1 | 2019-05-28T16:10:41.354248873Z    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:583)
dc_app-web-22_1 | 2019-05-28T16:10:41.354252879Z    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:500)
dc_app-web-22_1 | 2019-05-28T16:10:41.354257136Z    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:462)
dc_app-web-22_1 | 2019-05-28T16:10:41.354261220Z    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897)
dc_app-web-22_1 | 2019-05-28T16:10:41.354265061Z    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
dc_app-web-22_1 | 2019-05-28T16:10:41.354268934Z    at java.lang.Thread.run(Thread.java:748)


dc_app-web-21_1 | 2019-05-28T15:04:01.864509828Z 2019-05-28 23:04:01.864 logback [scheduling-1] ERROR o.s.s.s.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task.
dc_app-web-21_1 | 2019-05-28T15:04:01.864522784Z java.lang.ClassCastException: null
dc_app-web-21_1 | 2019-05-28T15:04:02.212740719Z 2019-05-28 23:04:02.212 logback [scheduling-1] ERROR o.s.s.s.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task.
dc_app-web-21_1 | 2019-05-28T15:04:02.212775550Z java.lang.ClassCastException: null
dc_app-web-21_1 | 2019-05-28T15:04:02.212780200Z 2019-05-28 23:04:02.212 logback [redisson-netty-1-3] WARN  i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
dc_app-web-21_1 | 2019-05-28T15:04:02.212785052Z io.netty.handler.codec.DecoderException: CommandDecoder.decode() must consume the inbound data or change its state if it did not decode anything.
dc_app-web-21_1 | 2019-05-28T15:04:02.212791539Z    at io.netty.handler.codec.ReplayingDecoder.callDecode(ReplayingDecoder.java:379)
dc_app-web-21_1 | 2019-05-28T15:04:02.212794942Z    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278)
dc_app-web-21_1 | 2019-05-28T15:04:02.212798122Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-21_1 | 2019-05-28T15:04:02.212801181Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-21_1 | 2019-05-28T15:04:02.212813072Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-21_1 | 2019-05-28T15:04:02.212816644Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-21_1 | 2019-05-28T15:04:02.212819773Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-21_1 | 2019-05-28T15:04:02.212822603Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-21_1 | 2019-05-28T15:04:02.212825516Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-21_1 | 2019-05-28T15:04:02.212828302Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-21_1 | 2019-05-28T15:04:02.212831177Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-21_1 | 2019-05-28T15:04:02.212834124Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-21_1 | 2019-05-28T15:04:02.212837979Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-21_1 | 2019-05-28T15:04:02.212840915Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-21_1 | 2019-05-28T15:04:02.212845119Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-21_1 | 2019-05-28T15:04:02.212848013Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-21_1 | 2019-05-28T15:04:02.212850940Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-21_1 | 2019-05-28T15:04:02.212853933Z    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
dc_app-web-21_1 | 2019-05-28T15:04:02.212856847Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-21_1 | 2019-05-28T15:04:02.212859622Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-21_1 | 2019-05-28T15:04:02.212862610Z    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
dc_app-web-21_1 | 2019-05-28T15:04:02.212865403Z    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
dc_app-web-21_1 | 2019-05-28T15:04:02.212868377Z    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:648)
dc_app-web-21_1 | 2019-05-28T15:04:02.212871087Z    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:583)
dc_app-web-21_1 | 2019-05-28T15:04:02.212874070Z    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:500)
dc_app-web-21_1 | 2019-05-28T15:04:02.212876821Z    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:462)
dc_app-web-21_1 | 2019-05-28T15:04:02.212879573Z    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897)
dc_app-web-21_1 | 2019-05-28T15:04:02.212882442Z    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
dc_app-web-21_1 | 2019-05-28T15:04:02.212889988Z    at java.lang.Thread.run(Thread.java:748)


dc_app-web-22_1 | 2019-05-29T03:21:34.269751045Z 2019-05-29 11:21:34.269 logback [redisson-netty-1-5] WARN  i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
dc_app-web-22_1 | 2019-05-29T03:21:34.269775301Z io.netty.handler.codec.DecoderException: java.lang.IndexOutOfBoundsException: Index: 18, Size: 18
dc_app-web-22_1 | 2019-05-29T03:21:34.269781319Z    at io.netty.handler.codec.ReplayingDecoder.callDecode(ReplayingDecoder.java:421)
dc_app-web-22_1 | 2019-05-29T03:21:34.269795521Z    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278)
dc_app-web-22_1 | 2019-05-29T03:21:34.269799462Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-29T03:21:34.269803279Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-29T03:21:34.269807414Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-22_1 | 2019-05-29T03:21:34.269811944Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-22_1 | 2019-05-29T03:21:34.269815876Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-29T03:21:34.269819996Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-29T03:21:34.269824023Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-22_1 | 2019-05-29T03:21:34.269828218Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-22_1 | 2019-05-29T03:21:34.269831820Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-29T03:21:34.269835580Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-29T03:21:34.269839139Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-22_1 | 2019-05-29T03:21:34.269850738Z    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
dc_app-web-22_1 | 2019-05-29T03:21:34.269854693Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-29T03:21:34.269858254Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-29T03:21:34.269863242Z    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
dc_app-web-22_1 | 2019-05-29T03:21:34.269867606Z    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
dc_app-web-22_1 | 2019-05-29T03:21:34.269871662Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
dc_app-web-22_1 | 2019-05-29T03:21:34.269875972Z    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
dc_app-web-22_1 | 2019-05-29T03:21:34.269880238Z    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
dc_app-web-22_1 | 2019-05-29T03:21:34.269884545Z    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
dc_app-web-22_1 | 2019-05-29T03:21:34.269888787Z    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:648)
dc_app-web-22_1 | 2019-05-29T03:21:34.269893035Z    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:583)
dc_app-web-22_1 | 2019-05-29T03:21:34.269896495Z    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:500)
dc_app-web-22_1 | 2019-05-29T03:21:34.269900431Z    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:462)
dc_app-web-22_1 | 2019-05-29T03:21:34.269930161Z    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897)
dc_app-web-22_1 | 2019-05-29T03:21:34.269942137Z    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
dc_app-web-22_1 | 2019-05-29T03:21:34.269947128Z    at java.lang.Thread.run(Thread.java:748)
dc_app-web-22_1 | 2019-05-29T03:21:34.269951320Z Caused by: java.lang.IndexOutOfBoundsException: Index: 18, Size: 18
dc_app-web-22_1 | 2019-05-29T03:21:34.269955532Z    at java.util.LinkedList.checkElementIndex(LinkedList.java:555)
dc_app-web-22_1 | 2019-05-29T03:21:34.269958475Z    at java.util.LinkedList.get(LinkedList.java:476)
dc_app-web-22_1 | 2019-05-29T03:21:34.269961296Z    at org.redisson.client.handler.CommandDecoder.decodeCommandBatch(CommandDecoder.java:219)
dc_app-web-22_1 | 2019-05-29T03:21:34.269964207Z    at org.redisson.client.handler.CommandDecoder.decodeCommand(CommandDecoder.java:140)
dc_app-web-22_1 | 2019-05-29T03:21:34.269966938Z    at org.redisson.client.handler.CommandDecoder.decode(CommandDecoder.java:108)
dc_app-web-22_1 | 2019-05-29T03:21:34.269980618Z    at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:502)
dc_app-web-22_1 | 2019-05-29T03:21:34.269985215Z    at io.netty.handler.codec.ReplayingDecoder.callDecode(ReplayingDecoder.java:366)
dc_app-web-22_1 | 2019-05-29T03:21:34.269989592Z    ... 28 common frames omitted
jupiter_888
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 3
    评论
RedissonKeys.Delete() 方法在Cluster模式下传入空数组导致的线程卡死问题
qq_40343117的博客
08-21 719
1、问题背景 最近在使用Redisson做项目的时候，发现服务启动正常，但无论怎么请求都不会有数据返回，并且没有任何异常抛出，导致整个服务处于一种看似正常运行，但早就被卡死的状态的发生。 2、问题排查 由于这个服务已经上线运行了三四年并无问题发生，所以导致这个现象发生的原因一定在最近更换的Redisson客户端中，通过排查发现代码中有一部分，取到的是一个空数组，并传入了RedissonKeys.Delete()方法中，代码大致如下： Config config = new Conf
Redisson简单学习
creaylei的小花园
06-05 2822
Redisson常见操作和典型应用场景
redisson的实现和优缺点
最新发布
m0_63102097的博客
05-19 1101
是一个基于 Redis 的 Java 驻内存数据网格解决方案，提供了丰富的分布式数据结构和功能，能够有效地解决可重入、可重试、超时释放以及主从一致性等问题。
基于Netty实现Redis协议的编码解码器
weixin_34400525的博客
03-19 465
Netty消息处理结构 上面是Netty的服务器端基本消息处理结构，为了便于初学者理解，它和真实的结构有稍许出入。Netty是基于NIO的消息处理框架，用来高效处理网络IO。处理网络消息一般走以下步骤 监听端口 Bind & Listen 接收新连接 Accept 通过连接收取客户端发送的字节流，转换成输入消息对象 Read & Decode 处理消息，生成输出消...
redis服务器响应超时,Redisson执行命令超时，已设置超时时间为60s，是否存在bug？...
weixin_32647107的博客
08-02 2861
redis集群规模：20个节点，10主、10从；17:21:00 [pool-57-thread-1] ERROR o.s.s.s.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduledtask.org.redisson.client.RedisTimeoutException: Redis server res...
redisson使用手册
01-19
手册还将分享一些使用Redisson的最佳实践，如连接池配置、数据结构选择、性能优化等方面的经验，帮助开发者避免常见问题，提升应用性能。 总之，Redisson使用手册是Java开发者深入理解和使用Redisson的重要参考资料...
redisson实现分布式锁原理
08-31
Redisson 是一个流行的 Java 客户端，用于与 Redis 数据库进行交互，它提供了丰富的数据结构和服务，包括分布式锁的实现。在本文中，我们将深入探讨 Redisson 如何实现分布式锁，以及其特点和机制。 分布式锁是多...
redisson实现分布式锁
12-16
Redisson的分布式锁是基于Redis实现的，利用Redis的高可用性、低延迟以及丰富的数据结构特性，可以有效地解决分布式环境下的锁问题。Redisson通过命令行接口（Command）将Java方法映射到Redis操作上，这样我们就可以...
redisson.rar
09-03
`Redisson`的分布式锁功能可以解决这个问题。分布式锁允许在多线程或多节点之间进行同步，确保同一时刻只有一个线程或节点能执行特定操作，从而避免了编号冲突。 在`springboot`应用中，可以创建一个服务类，使用`...
redisson_demo.rar
03-17
在本项目"redisson_demo.rar"中，我们探讨了如何利用Spring Cloud、Redisson以及Feign来构建一个高效的分布式锁系统，以实现多节点环境下的秒杀功能。这个系统的关键在于处理并发请求，确保数据的一致性和事务性，...
Communications link failure during commit(). Transaction resolution unknown.
cihuan0804的博客
07-06 1万+
13:37:06.443 [pool-10-thread-1] ERROR o.s.s.s.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task. org.springframework.tran...
Unexpected error occurred in scheduled task
热门推荐
掐指一算乀缺钱
11-01 3万+
定时任务出现这个错误,是因为是因为@Scheduled注解方式级别高于资源注入级别,导致资源注入失败. 示例: @Component @Lazy(value = false) public class AlertTask { @Autowired IOTDeviceService iOTDeviceService; /** * @Description ...
No Assembler service found - please make sure that the right jars are in your classpath
Fanx繁星
11-30 1644
报错信息 [ERROR]2021-11-30 09:53:35.439[org.springframework.scheduling.support.TaskUtils$LoggingErrorHandler:95] - Unexpected error occurred in scheduled task com.atomikos.icatch.SysException: No Assembler service found - please make sure that the right jars a
java.lang.NoClassDefFoundError: org/redisson/client/protocol/decoder/ListMultiDecoder2
//Case
02-04 3209
Caused by: java.lang.NoClassDefFoundError: org/redisson/client/protocol/decoder/ListMultiDecoder2 at org.redisson.spring.data.connection.RedissonConnection.(RedissonConnection.java:1259) ~[redisson-spring-data-22-3.13.1.jar:3.13.1] at org.redisson.spring.d
一个低级错误引发Netty编码解码中文异常
weixin_30567225的博客
10-03 2266
前言 最近在调研Netty的使用，在编写编码解码模块的时候遇到了一个中文字符串编码和解码异常的情况，后来发现是笔者犯了个低级错误。这里做一个小小的回顾。 错误重现 在设计Netty的自定义协议的时候，发现了字符串类型的属性，一旦出现中文就会出现解码异常的现象，这个异常并不一定出现了Exception，而是出现了解码之后字符截断出现了人类不可读的字符。编码和解码器的实现如下： // 实体 ...
redissionClient报错问题
淋雨西河的博客
08-04 1万+
08-04 17:38 ERROR - o.r.client.handler.CommandDecoder Unable to decode data. channel: [id: 0xf7e21491, L:/192.168.1.145:65196 - R:192.168.1.99/192.168.1.99:6379], reply: ReplayingDecoderByteBuf(ridx=654, widx=654), command: (LINDEX), params: [task-categ.
Netty源码分析-ReplayingDecoder
大新博客
07-12 1267
ReplayingDecoder可以重复解码的解码器，此类的核心原理是内部包含了一个ReplayingDecoderByteBuf，当读取字节不够时则抛出异常，ReplayingDecoder捕获异常还原读取readerIndex然后等待Netty下一次事件继续读取。 ReplayingDecoderByteBuf集成了Bytebuf，它代理了ByteBuf当中读取的方法。 final...
redis 使用redisson缓存api模板
Qensq的博客
04-11 1471
import org.redisson.api.RLock; import java.util.List; import java.util.Map; import java.util.Set; import java.util.concurrent.TimeUnit; /** * @Author: Garcia * @CreateDate: 2021/04/10 17:45 * @Description: what it is class? */ public interface Cache.
redisson死锁问题
03-13
Redisson是一个基于Redis的Java驻留内存数据网格（In-Memory Data Grid）和分布式锁框架。在使用Redisson时，可能会遇到死锁问题。 死锁是指两个或多个线程在互相等待对方释放资源的情况下无限期地阻塞的现象。在Redisson中，死锁问题通常发生在分布式锁的使用过程中。 造成Redisson死锁问题的原因可能有以下几点： 1. 程序逻辑错误：在使用分布式锁时，如果程序逻辑不正确，可能会导致死锁。例如，一个线程获取了锁但没有释放，导致其他线程无法获取锁而陷入死锁状态。 2. 锁超时设置不合理：在使用Redisson分布式锁时，可以设置锁的超时时间。如果超时时间设置过长，可能会导致其他线程长时间等待而出现死锁。 3. 高并发场景下的竞争：在高并发场景下，多个线程同时请求获取锁，可能会导致竞争激烈，从而增加了死锁的风险。 为了避免Redisson死锁问题，可以采取以下措施： 1. 合理设计程序逻辑：确保在获取锁后及时释放锁，避免出现死锁情况。 2. 设置合理的锁超时时间：根据实际业务需求，设置适当的锁超时时间，避免长时间等待而导致死锁。 3. 使用可重入锁：Redisson提供了可重入锁（ReentrantLock）的实现，可以避免同一个线程重复获取锁而导致死锁。 4. 使用RedLock算法：RedLock是Redisson提供的一种分布式锁算法，可以在多个Redis节点之间协作，提高分布式锁的可靠性和安全性。
评论 3
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值