[
https://issues.apache.org/jira/browse/PROTON-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986113#comment-14986113
]
Ken Giusti commented on PROTON-1003:
------------------------------------
The problem is caused by a leak of the pn_reactor_t instance owned by the
container.
I think there is a circular reference introduced by the pn_link_t's endpoint
handler property. If I set recv.link.handler = None, the pn_reactor_t is
reclaimed.
Not sure of where the best place to add the clearing of the handler property.
The endpoint object never has its __del__ method called, which would be the
natural place to put it.
Maybe we add it to link->close() and force the user to explicitly close the
links when done? Kinda sucky.
This doesn't appear to be an SSL issue - assigning to Gordon the python reactor
guy.
> ssl transport layer does not define an error handler
> ----------------------------------------------------
>
> Key: PROTON-1003
> URL: https://issues.apache.org/jira/browse/PROTON-1003
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.10
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Fix For: 0.11
>
>
> When the local process times out an ssl based connection due to lack of
> heartbeats from its peer, the underlying socket is never closed. The cause of
> this appears to be that the ssl transport layer doesn't define an error
> handler, which is what is used to notify it of the locally initiated timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
