yujb-come opened a new issue, #455:
URL: https://github.com/apache/rocketmq-client-cpp/issues/455

   I used producer to send sync message , sometimes it will send failed, 
   error info like : ‘GetTransport of:x.x.x.x:yyyy get timed_mutex timeout' 'No 
route information of this topic:xxx' 
   
   [Error Detail]
   [2023-Sep-09 15:59:49.902624](error):GetTransport of:172.26.89.216:10911 get 
timed_mutex timeout[CreateTransport:307]
   [2023-Sep-09 15:59:49.902885](error):send failed of 
times:1,brokerName:broker-a[sendDefaultImpl:424]
   [2023-Sep-09 15:59:49.902979](error):could not find property 
mq[selectOneMessageQueue:156]
   [2023-Sep-09 15:59:49.903595](error):GetTransport of:172.26.89.216:10911 get 
timed_mutex timeout[CreateTransport:307]
   [2023-Sep-09 15:59:49.903746](error):send failed of 
times:3,brokerName:broker-a[sendDefaultImpl:424]
   [2023-Sep-09 15:59:49.903823](error):could not find property 
mq[selectOneMessageQueue:156]
   [2023-Sep-09 15:59:49.904193](error):GetTransport of:172.26.89.216:10911 get 
timed_mutex timeout[CreateTransport:307]
   [2023-Sep-09 15:59:49.904330](error):send failed of 
times:5,brokerName:broker-a[sendDefaultImpl:424]
   [2023-Sep-09 15:59:49.904409](error):msg: No route info of this topic: 
audio-upload-topic,error:-1,in file 
</root/src/rocketmq-client-cpp-release-2.2.0/src/producer/DefaultMQProducerImpl.cpp>
 line:434[send:137]
   
   [Environment]
   Centos 7
   rocketmq-client-cpp-release-2.2.0.tar.gz
   libevent-release-2.1.11-stable.zip
   
   
   I referred to the previous issue 
https://github.com/apache/rocketmq-client-cpp/issues/211
   It is said that this is a bug in libevent, and upgrade to version 2.1. X can 
solve the problem,
   But why does this error still occur when we are currently using 
libevent-release-2.1.11-stable.zip .
   Is there any other reason that could cause this error to occur
   
   thankyou~


-- 
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