Getting timeout MessagingError
See original GitHub issue- Package Name: @azure/event-hubs
- Package Version: 5.3.1
- Operating system: ubuntu docker
- nodejs
- version: 14.15
Describe the bug
Getting a lot of:
MessagingError: The request with message_id "99a003b3-e410-475b-acd0-461d113fc07a" timed out. Please try again later. at Object.translate (/src/node_modules/@azure/core-amqp/dist/index.js:856:23)
What does this error means?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
MessagingError [OperationTimeoutError]: Unable to create the ...
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to...
Read more >Using @azure/event-hubs sending message always run into a ...
I get to the point when the user/client needs allow the azure application. But after then when I am using the created producer...
Read more >Powershell Error The client got a timeout from the network ...
I am getting below error messages. Log Name: Microsoft-Windows-WinRM/Operational Source: Microsoft-Windows-WinRM. Date: 4/5/2018 4:11:26 PM
Read more >JIRA not taking the Emails - Atlassian Community
Logs says ServiceRunner Messaging Error when MailPullerWorker pulls emails from ... port: outlook.office365.com, 993; timeout 50000.
Read more >@azure/core-amqp - NET
The value to be resolved with after a timeout of t milliseconds. Returns Promise<T>. Resolved promise. isMessagingError.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, sorry about the delay. yes I’m getting the error from the
processError
handler, and yes its invoked continuously without any events coming in to our client, and yes on reset it was resolved until it happened again The stack trace:Closing as this was fixed by #15042 and included in
@azure/event-hubs
versions 5.5.1+