10. 成功解决:io.netty.channel.ChannelPipelineException: ***Handler is not a @Sharable handler, so can't be added or removed multiple times.

简介: 使用 SpringBoot 集成 Netty 时,报如下错误:io.netty.channel.ChannelPipelineException: ***Handler is not a @Sharable handler, so can't be added or removed multiple times.

8b6d6bba21332fef2a9927834e454b88_image_auth_key=1686704139-gAx4zSWSibzxX1ZHNdu7At-0-98cea666149119a7d8b60ce273115188&file_size=332738.png

❤️ 个人主页:水滴技术
🌸 订阅专栏:成功解决 BUG 合集
🚀 支持水滴:点赞👍 + 收藏⭐ + 留言💬

问题描述

使用 SpringBoot 集成 Netty 时,报如下错误:

io.netty.channel.ChannelPipelineException: ***Handler is not a @Sharable handler, so can't be added or removed multiple times.
  at io.netty.channel.DefaultChannelPipeline.checkMultiplicity(DefaultChannelPipeline.java:600) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.DefaultChannelPipeline.addLast(DefaultChannelPipeline.java:202) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.DefaultChannelPipeline.addLast(DefaultChannelPipeline.java:381) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at ***ChannelInitializer.initChannel(GeneralChannelInitializer.java:27) ~[classes/:na]
  at ***ChannelInitializer.initChannel(GeneralChannelInitializer.java:15) ~[classes/:na]
  at io.netty.channel.ChannelInitializer.initChannel(ChannelInitializer.java:129) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.ChannelInitializer.handlerAdded(ChannelInitializer.java:112) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.AbstractChannelHandlerContext.callHandlerAdded(AbstractChannelHandlerContext.java:938) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.DefaultChannelPipeline.callHandlerAdded0(DefaultChannelPipeline.java:609) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.DefaultChannelPipeline.access$100(DefaultChannelPipeline.java:46) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.DefaultChannelPipeline$PendingHandlerAddedTask.execute(DefaultChannelPipeline.java:1463) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.DefaultChannelPipeline.callHandlerAddedForAllHandlers(DefaultChannelPipeline.java:1115) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.DefaultChannelPipeline.invokeHandlerAddedIfNeeded(DefaultChannelPipeline.java:650) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.AbstractChannel$AbstractUnsafe.register0(AbstractChannel.java:514) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.AbstractChannel$AbstractUnsafe.access$200(AbstractChannel.java:429) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.AbstractChannel$AbstractUnsafe$1.run(AbstractChannel.java:486) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:174) [netty-common-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java) [netty-common-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:167) [netty-common-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java) [netty-common-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) [netty-common-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) [netty-transport-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.82.Final.jar:4.1.82.Final]
  at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.82.Final.jar:4.1.82.Final]
  at java.lang.Thread.run(Thread.java:748) [na:1.8.0_251]

原因分析

错误信息的意思是自定义的 Handler 不是 @Sharable ,所以不能多次添加或删除。这是为什么呢,看了下源码找到了答案。

66d2f218b680b84a2f191e7a8fa54226_image_auth_key=1686704155-312YhTxUGPqLmPkPN9Wqyz-0-78de83f76fcac094ab112972af2dc1ac&file_size=59402.png

注释的大体意思是:

可以将带该注释的 ChannelHandler 的同一个实例多次添加到一个或多个 ChannelPipeline ,而不存在竞争条件。
如果未指定该注解,每次添加 ChannelPipeline 时必须创建一个新的ChannelHandler实例,因为它具有成员变量等非共享状态。

解决方案

有两种解决方案:

方案一:增加@ChannelHandler.Sharable 注解

在自定义的 Handler 上增加 @ChannelHandler.Sharable 注解。

81e8147e23d6fed66562a542ded99c89_image_auth_key=1686704173-v36TgXiYM6UNsCyBwXoSg1-0-f546dbd9650e8572cb36820b809ab761&file_size=10877.png

方案二:

在 pipelin 中改为 new 创建实例。

2daa1b8d32e5424f10a5033bb67e822e_image_auth_key=1686704185-31z6CXkFhtwJAYWMJAFo4B-0-2316ca4fd7c5cc5f73b776454a9567c2&file_size=65753.png


热门专栏

👍 《IDEA 教程:从入门到精通

👍 《Java 教程:从入门到精通

👍 《MySQL 教程:从入门到精通

相关文章
|
7月前
|
Web App开发 前端开发
【前端异常】Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
【前端异常】Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
464 0
|
安全 Java 数据库连接
Java报错javax.net.ssl.SSLException MESSAGE: closing inbound before receiving peer‘s close_notify解决方法
Java报错javax.net.ssl.SSLException MESSAGE: closing inbound before receiving peer‘s close_notify解决方法
Java报错javax.net.ssl.SSLException MESSAGE: closing inbound before receiving peer‘s close_notify解决方法
|
搜索推荐
【异常】Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information: /127.0.0.1:9300
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information: /127.0.0.1:9300
1631 0
【异常】Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information: /127.0.0.1:9300
|
9月前
|
数据安全/隐私保护
Do Sync Disk 0 Part 0 Failed, code=S3_F42, msg=Sync Failed after retry 5 times
Do Sync Disk 0 Part 0 Failed, code=S3_F42, msg=Sync Failed after retry 5 times
144 1
|
11月前
|
Java Spring
Redisson BUG: Failed to submit a listener notification task. Event loop shut down?
Redisson BUG: Failed to submit a listener notification task. Event loop shut down?
840 0
|
网络协议 Java
filebeat:Failed to publish events caused by: write tcp 5044: write: connection reset by peer
filebeat:Failed to publish events caused by: write tcp 5044: write: connection reset by peer
330 0
filebeat:Failed to publish events caused by: write tcp 5044: write: connection reset by peer
|
NoSQL Java Redis
JedisDataException: Please close pipeline or multi block before calling this method
JedisDataException: Please close pipeline or multi block before calling this method
155 0
multi-thread handling for batch request
Created by Wang, Jerry, last modified on Feb 13, 2017
66 0
multi-thread handling for batch request
|
Java
OData debug - Java client - why my batch request fails
OData debug - Java client - why my batch request fails
82 0
OData debug - Java client - why my batch request fails
JMeter: Socket Exception in high concurrent parallel request
JMeter: Socket Exception in high concurrent parallel request
340 0
JMeter: Socket Exception in high concurrent parallel request