[jira] [Created] (PROTON-641) pn_connection_t leaked when links not closed

Gordon Sim created PROTON-641: - Summary: pn_connection_t leaked when links not closed Key: PROTON-641 URL: https://issues.apache.org/jira/browse/PROTON-641 Project: Qpid Proton Issue Type: Bug

[jira] [Updated] (PROTON-641) pn_connection_t leaked when links not closed

[ https://issues.apache.org/jira/browse/PROTON-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-641: -- Attachment: proton_leak.cpp Running attached test under valgrind gives: ==17718== ==17718== HEAP

Having a collector per transport (in addition to per connection)

I've been looking at fixing PROTON-635 (Not enough PN_TRANSPORT events being generated for a driver). It occurs to me that since the lifecycle of pn_transport_t and pn_connection_t objects are completely independent it makes sense (to me at least) that PN_TRANSPORT events get sent to a transport

[jira] [Updated] (PROTON-635) PN_TRANSPORT events not generated in enough places

[ https://issues.apache.org/jira/browse/PROTON-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-635: --- Summary: PN_TRANSPORT events not generated in enough places (was: PN_TRANSPORT event not

[jira] [Updated] (PROTON-635) PN_TRANSPORT events not generated in enough places

[ https://issues.apache.org/jira/browse/PROTON-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-635: --- Description: In writing a custom driver for Proton I noticed thatthe new events code does