When qpid Python library gets an exception from the broker (like ACL authorization failure), the library can't recover from it. Namely, when catching raised exception, it is convenient to close affected session and connection. An attempt to do so re-raises the same exception that has been already caught.
Does that mean some session and/or connection leak?
Are that session and/or connection properly closed?
How to prevent re-raising the exception?
- MRG Messaging (any version)
- qpid Python client
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.