Forcibly clear connection pool after every request
Neutron client is ending up with bad socket descriptors
which causes the behavior including trying to read from
the socket that amqp currently holds etc. A temporary
solution is to clear the connection pool so we get a
fresh socket built for every request.
Reviewed: https:/ /review. openstack. org/49210 github. com/openstack/ python- neutronclient/ commit/ e6a9f79066943b7 5e2c60b0165533d 5886cc9cd8
Committed: http://
Submitter: Jeremy Stanley (<email address hidden>)
Branch: master
commit e6a9f79066943b7 5e2c60b0165533d 5886cc9cd8
Author: Davanum Srinivas <email address hidden>
Date: Tue Oct 1 12:27:32 2013 -0400
Forcibly clear connection pool after every request
Neutron client is ending up with bad socket descriptors
which causes the behavior including trying to read from
the socket that amqp currently holds etc. A temporary
solution is to clear the connection pool so we get a
fresh socket built for every request.
Closes-Bug: 1229475
Change-Id: I43b1fe535bc5bd 1fc726c97a293bf 7912cd7ef1e