[ 
https://issues.apache.org/jira/browse/PROTON-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Giusti updated PROTON-1090:
-------------------------------
    Attachment: cputest.py

reproducer

let it connect to qdrouterd, then restart qdrouterd.  cputest.py's cpu will hit 
100% once the connection is re-established.

Reproduces reliably on fedora22 after a couple of restarts.



> 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)

Reply via email to