You are viewing a plain text version of this content. The canonical link for it is here.

Posted to proton@qpid.apache.org by "Fabien CHEVALIER (JIRA)" <ji...@apache.org> on 2014/11/30 19:44:12 UTC

[jira] [Updated] (PROTON-761) 100% CPU with multiple subscriptions

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

Fabien CHEVALIER updated PROTON-761:
------------------------------------
    Attachment: infinite-loop.c

> 100% CPU with multiple subscriptions
> ------------------------------------
>
>                 Key: PROTON-761
>                 URL: https://issues.apache.org/jira/browse/PROTON-761
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.8
>            Reporter: Fabien CHEVALIER
>         Attachments: infinite-loop.c
>
>
> Calling pn_messenger_subscribe() twice (which seems to be perfectly valid) can result in proton hanging at 100% cpu, when one of the two sources is unreachable.
> To reproduce, start the attached test case against a pristine ActiveMQ copy (./bin/activemq console). Proton will go nuts when trying to connect to the unavailable amqp://localhost:15672/ganymede instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)