Skip to content

Conversation

@l0lawrence
Copy link
Member

@l0lawrence l0lawrence commented Mar 18, 2024

Handling of service initiated detach errors when the error condition is None as it was causing the code to stall after sending out the responding detach.

Repro is to disable an entity and within process-incoming-frames frame[2][0] if it is a "link-detach-forced" set frame[2] = None

frame -

<- DetachFrame(handle=2, closed=True, error=None)

@l0lawrence
Copy link
Member Author

/azp run python - servicebus - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kashifkhan
Copy link
Member

We are raising a AMQPLinkError here in the case of when we get a link detach from the service (uninitiated by the client).

There is potentially another way to handle this by attaching right away (instead of closing the connection and going from scratch) when we receive such a detach. I wonder if doing that would cause some other scenario to fail

@azure-sdk
Copy link
Collaborator

azure-sdk commented Mar 18, 2024

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-servicebus

@kashifkhan
Copy link
Member

/azp run python - servicebus - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kashifkhan
Copy link
Member

/azp run python - servicebus - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kashifkhan kashifkhan marked this pull request as ready for review March 20, 2024 00:29
@swathipil swathipil merged commit 576393d into Azure:main Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants