-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redirect error not surfaced to client #358
Comments
Thanks for providing such detailed info, it's super helpful. I think that IoT is sending a malformed Per https://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#doc-idp315568 "Note that if the application chooses not to create a terminus, the session endpoint will still create a link endpoint and issue an attach indicating that the link endpoint has no associated local terminus. In this case, the session endpoint MUST immediately detach the newly created link endpoint." We can see that the peer didn't create a terminus ( I'm not sure who owns this part of IoT but will ask around. I'll leave this open for the time being in case more info is required. |
@jeolted as this is an issue with the service, can you please open an issue with Azure support. |
Unfortunately, my support plan doesn't allow me to open technical tickets on services. |
Understood. I've routed this internally to the IoT Hub folks to investigate further. |
Thanks! |
I have an issue where an amqp client connecting to Azure IoT Hub is expected to receive a redirect to EventHub. The IoT Hub sends an Attach frame with a redirect error but the go-amqp lib doesn't recognize it and drops it.
I'm not sure who's in the wrong here. The attach frame we get back expects to have the role sender but it has receiver. The session mux doesn't find the link in linksByKey map since the role is not what it expected.
I've written a simple test for reproduction of the error:
The log from amqp lib when running the test:
The text was updated successfully, but these errors were encountered: