sohutv / sohutv/mqcloud

客户端在生产消息时偶尔报发送失败报错,报错信息见正文

Open
#51 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
2.2k
Forks
285
PR merge metrics
No merged PRs in 30d

Description

2023-11-21 07:56:56.709 ERROR [DubboServerHandler-172.20.3.143:58439-thread-199] [TID:1b4771c8afc94ee7b46c5a9b28679de4.620.17005246136686327] c.sohu.tv.mq.rocketmq.RocketMQProducer Line:284 - send error
在生产消息时,偶尔报如上错误,在故障点,排查rocketmq broker均无资源凸峰,但是有如下error。

2023-11-21 07:57:08 ERROR NettyServerNIOSelector_3_2 - processRequestWrapper response to /172.16.14.111:24829 failed
io.netty.channel.StacklessClosedChannelException: null ----->这个error,我估计是不是客户端发送失败关闭了连接,因此broker返回数据失败。

烦请给个send error报错的解决思路。

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with RocketMQProducer at line 284 and correlate its “send error” timestamp with the broker’s NettyServerNIOSelector_3_2 StacklessClosedChannelException. Review the client and broker logs around the affected connection and determine whether the failure is caused by a closed client connection or another transport condition. Done means documenting a reproducible cause and a concrete remediation path.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.