apache / apache/rocketmq-client-cpp
"GetTransport of:x.x.x.x:yyyy get timed_mutex timeout" and "No route info of this topic" error while sending mq message
- Vorherrschende Sprache
- C++
- Sterne
- 393
- Forks
- 167
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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 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 possibilities that could cause this error to occur
thankyou~
Beitragsleitfaden
Rechercherichtung
Start in src/producer/DefaultMQProducerImpl.cpp around CreateTransport at line 307 and send at line 434. Reproduce the timeout with libevent 2.1.11, then compare the behavior with issue #211 and the reported environment. Done means identifying a confirmed cause or required configuration and documenting the resolution.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- cpp
- Bereich
- networking
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100