qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-4133) Non-responsive peer in federated link can result in entire cluster shutdown
Date Tue, 17 Jul 2012 21:21:34 GMT

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

Alan Conway resolved QPID-4133.

    Resolution: Fixed

Merged to 0.18 r1362653
> Non-responsive peer in federated link can result in entire cluster shutdown
> ---------------------------------------------------------------------------
>                 Key: QPID-4133
>                 URL: https://issues.apache.org/jira/browse/QPID-4133
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Clustering
>    Affects Versions: 0.12
>            Reporter: Jason Dillaman
>            Assignee: Alan Conway
>         Attachments: jira-4133.patch
> If a federated link is established to a source broker that is slow to respond with the
AMQP handshake, the destination broker cluster will shutdown with an "Unknown connection"
> Exception constructed: Unknown connection: Frame[BEbe; channel=0; {ClusterConnectionDeliverDoOutputBody:
limit=2048; }] control (qpid/cluster/Cluster.cpp:542)
> Steps to Reproduce:
> 1. Configure a clustered broker
> 2. Start netcat in listen mode (nc -l 6000)
> 3. Add a route between the clustered broker and nc (qpid-route queue add localhost:5672
localhost:6000 amq.fanout foo)
> 4. Clustered broker shuts down

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message