lijie123bes opened a new issue, #7883:
URL: https://github.com/apache/rocketmq/issues/7883

   ### Before Creating the Bug Report
   
   - [X] I found a bug, not just asking a question, which should be created in 
[GitHub Discussions](https://github.com/apache/rocketmq/discussions).
   
   - [X] I have searched the [GitHub 
Issues](https://github.com/apache/rocketmq/issues) and [GitHub 
Discussions](https://github.com/apache/rocketmq/discussions)  of this 
repository and believe that this is not a duplicate.
   
   - [X] I have confirmed that this bug belongs to the current repository, not 
other repositories of RocketMQ.
   
   
   ### Runtime platform environment
   
   centos7.9
   
   ### RocketMQ version
   
   4.3.1
   
   ### JDK Version
   
   _No response_
   
   ### Describe the Bug
   
   org.apache.rocketmq.remoting.exception.RemotingTooMuchRequestException: 
sendDefaultImpl call timeout at 
org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.sendDefaultImpl(DefaultMQProducerImpl.java:612)
 ~[rocketmq-client-4.3.1.jar:4.3.1] at 
org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:1253)
 ~[rocketmq-client-4.3.1.jar:4.3.1] at 
org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:1203)
 ~[rocketmq-client-4.3.1.jar:4.3.1] at 
org.apache.rocketmq.client.producer.DefaultMQProducer.send(DefaultMQProducer.java:214)
 ~[rocketmq-client-4.3.1.jar:4.3.1]
   
   ### Steps to Reproduce
   
   [NettyClientSelector_1] INFO RocketmqRemoting.info 
(Slf4jLoggerFactory.java:95) closeChannel: close the connection to remote 
address[] result: true
   
   ### What Did You Expect to See?
   
   connect normally
   
   
   ### What Did You See Instead?
   
   RemotingTooMuchRequestException
   
   ### Additional Context
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to