[
https://issues.apache.org/jira/browse/PROTON-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087502#comment-15087502
]
Pavel Moravec commented on PROTON-1090:
---------------------------------------
Yet another observation: the problem sounds to be on link level, not connection
level (I *think*).
I reproduced the same when having link routing in qdrouterd to qpid C++ broker,
and the reproducer script in fact created a link via qdrouterd to qpidd. Then I
was bouncing qpid _broker_. Not qdrouterd but qpidd. With lower probability
than bouncing qdrouterd, I got spinning CPU and same backtraces.
> BlockingConnection client spins at 100% cpu on reconnect
> --------------------------------------------------------
>
> Key: PROTON-1090
> URL: https://issues.apache.org/jira/browse/PROTON-1090
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c, python-binding
> Affects Versions: 0.9.1, 0.12.0
> Reporter: Ken Giusti
> Priority: Blocker
> Fix For: 0.12.0
>
> Attachments: cputest.py
>
>
> Attached is a simple python client that connects to a server and waits
> forever for a message to be received, reconnecting on connection failure.
> When the server is restarted (in my case I'm using qdrouterd), the client
> reconnects then pins the cpu at 100%. It appears as if the
> BlockingConnection.wait() method in util.py is the source of the busy loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
