[jira] [Commented] (QPID-4133) Non-responsive peer in federated link can result in entire cluster shutdown

2012-07-17 Thread Justin Ross (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416538#comment-13416538
 ] 

Justin Ross commented on QPID-4133:
---

Reviewed by Alan and Gordon.  Approved for 0.18.

 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 error.  
 Exception constructed: Unknown connection: Frame[BEbe; channel=0; 
 {ClusterConnectionDeliverDoOutputBody: limit=2048; }] control 
 2.0.0.0:22138-14 (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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4133) Non-responsive peer in federated link can result in entire cluster shutdown

2012-07-13 Thread Alan Conway (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413794#comment-13413794
 ] 

Alan Conway commented on QPID-4133:
---

Jason's patch is good, request merge to 0.18 branch.

 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 error.  
 Exception constructed: Unknown connection: Frame[BEbe; channel=0; 
 {ClusterConnectionDeliverDoOutputBody: limit=2048; }] control 
 2.0.0.0:22138-14 (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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4133) Non-responsive peer in federated link can result in entire cluster shutdown

2012-07-13 Thread Alan Conway (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413944#comment-13413944
 ] 

Alan Conway commented on QPID-4133:
---

Fixed on trunk, request permission for 0.18 branch


r1361321 | aconway | 2012-07-13 14:33:23 -0400 (Fri, 13 Jul 2012) | 4 lines

QPID-4133: (Jason Dillaman) Non-responsive peer in federated link can result in 
entire cluster shutdown

Fix is to not start link processing until the connection is open.



 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 error.  
 Exception constructed: Unknown connection: Frame[BEbe; channel=0; 
 {ClusterConnectionDeliverDoOutputBody: limit=2048; }] control 
 2.0.0.0:22138-14 (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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org