rabbit/qpid connection pool implementation is not safe
Bug #1397925 reported by
Mehdi Abaakouk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.messaging |
Fix Released
|
Undecided
|
Mehdi Abaakouk |
Bug Description
Hi,
The current implementation of the connection pool is not, it relies on a global state (a class variable). And can be broken in case of two transports object use the same broker, when one of the transport is 'cleanup' it destroy the pool and then break the remaining transport object.
Obviously, it's not very useful to create two transports object to the same broker.
Cheers
Changed in oslo.messaging: | |
milestone: | none → 1.5.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/138029
Review: https:/