Details
-
Bug
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
proton-c-0.28.0, proton-c-0.30.0
-
None
Description
Starting in proton 0.28.0 and verified in 0.29.0b1 (pre-release) I can confirm following issue:
from proton.utils import BlockingConnection c = BlockingConnection(YOUR_ADDRESS) c.close() # ^^ FINE, all file descriptors closed properly from proton.utils import BlockingConnection c = BlockingConnection(YOUR_ADDRESS) s = c.create_sender(YOUR_EXCHANGE) s.close() c.close() # ^^ leaks the socket file descriptor - connection not closed properly (ls /proc/YOUR_PID/fd to verify)
Version 0.27.0 is not affected by this issue.
Having a quick look at the proton bindings, this very well might be bug in the qpid proton library itself, not the python bindings!
Attachments
Issue Links
- is duplicated by
-
PROTON-2176 CLOSE_WAIT after BlockingSender close
- Reopened
- relates to
-
PROTON-2220 Add tests for recently fixed leaks in Python binding
- Closed
- links to