Skip to content

[ServiceBus] Making Sender/Receiver non-usable #15085

Closed

Description

Once the sender/receiver get closed, we propose not to allow reusing sender/receiver for the purpose of simplified amqp connection/link life cycle management and this aligns with other languages.

question:
that kind of error should we raise?
a customized error like "HandlerAlreadyClose" or ValueError

taking IOBase as an reference:
https://docs.python.org/3/library/io.html#io.IOBase.close

close()
Flush and close this stream. This method has no effect if the file is already closed. Once the file is closed, any operation on the file (e.g. reading or writing) will raise a ValueError.
As a convenience, it is allowed to call this method more than once; only the first call, however, will have an effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Service Busblocking-releaseBlocks release

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions