[
https://issues.apache.org/jira/browse/PROTON-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089308#comment-15089308
]
ASF subversion and git services commented on PROTON-1090:
---------------------------------------------------------
Commit 25d39a8e9cbf4846f23e4e58175d902924ec1a30 in qpid-proton's branch
refs/heads/master from [~gsim]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=25d39a8 ]
PROTON-1090: fix reactor timer pipe cleanup to prevent 100% cpu spin
> 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)
