[EventHub] ErrorCodes.UnknownError: Connection in an unexpected error state.
See original GitHub issueWe are running live Tests against other clouds like US Gov and Azure China Cloud. The goal is to check whether new azure sdk package work with other clouds or not.
Error Description:
When running the test test_send.py::test_send_with_partition_key and its async test in windows2019_36
on China
cloud, it runs failed and the error message is shown as following, for more details please check here:
Expected Behavior:
Test test_send.py::test_send_with_partition_key
passed in windows2019_36
on China
cloud.
In the local test, the probability of passing is 50%
.
@benbp , @jameszliao-msft , @lmazuel , @lilyjma , @ramya-rao-a and @annatisch for notification.
Issue Analytics
- State:
- Created 2 years ago
- Comments:24 (24 by maintainers)
Top Results From Across the Web
IoT hub AMQP connection closed error - Microsoft Q&A
ConnectionClose('ErrorCodes.UnknownError: Connection in an unexpected error state.') Traceback (most recent call last): File "c:\Users\B00760928 ...
Read more >Azure event Hub connection is closed error - Stack Overflow
I see something like the following error while using azure event hub to send event message. But as I see in the azure...
Read more >Azure Event hub input error in Microsoft Cloud Services add on
Can you please tell me what entitlements you have given to get this working? I am encountering the same errors. LinkDetach("ErrorCodes.
Read more >Azure Event Hubs client library for Python - NET
Obtain a connection string¶. For the Event Hubs client library to interact with an Event Hub, it will need to understand how to...
Read more >[azure-eventhub] Failure: sending socket failed. errno=104 ...
engineapi | WARNING [2022-07-27 07:00:50,106] connection.py:256 ConnectionClose('ErrorCodes.UnknownError: Connection in an unexpected error state.')
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 Free
Top 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
@v-xuto Thanks for testing this out! I was actually able to reproduce this error locally when testing against an EH namespace where the location is set far away and has a long round trip (specifically, Australia). I’m currently debugging right now to see if we’re retrying incorrectly or whether there’s a problem elsewhere. Will have more updates to you in the next week.
Hey @v-xuto! Just wanted to give you an update: I believe that the issue had to do with our retry logic in our test. I have a PR out to fix this and am working through a few comments on the PR. Hoping to have this merged by next week. Thanks @mikeharder for your suggestions on retry and reproducing with location set to Australia!
More details: We were using the underlying
uamqp
ReceiveClient to receive in the test (which doesn’t have the retry logic), rather than the EH Consumer Client (which has the retry logic). So, this should only be an issue in our test and not an issue with our SDK. Once I added the retry logic to the test, I was no longer getting this error.