[
https://issues.apache.org/jira/browse/QPID-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139152#comment-15139152
]
Brian Bouterse commented on QPID-7053:
--------------------------------------
I wrote a patch and pushed it to my fork on github. I've tested the kombu
changes and it works as expected.
the branch with my changes: https://github.com/bmbouter/qpid/tree/qpid-7053
the diff of my branch against trunk:
https://github.com/apache/qpid/compare/trunk...bmbouter:qpid-7053?expand=1
Note: Do not try to move the __setattr__ and registration methods to live on
Endpoint instead. It won't work! I already spent an hour trying to figure it
out so I recommend taking this patch as-is.
> Exception Notifier Callback
> ---------------------------
>
> Key: QPID-7053
> URL: https://issues.apache.org/jira/browse/QPID-7053
> Project: Qpid
> Issue Type: Improvement
> Components: Python Client
> Affects Versions: 0.32
> Reporter: Brian Bouterse
>
> When making effective use of the message_received callback handler added with
> QPID-5799, an unintended side-effect occurs regarding exception handling.
> The user registers the message_recieved callback using
> set_message_received_handler and then only calls back into qpid.messaging
> when it was told to do so. As a result when a ConnectionError occurs it is
> not raised. This effectively deadlocks the receiver since it can't know to
> call into qpid.messaging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
