Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 506293

Summary: Framing error brings down cluster.
Product: Red Hat Enterprise MRG Reporter: William Henry <whenry>
Component: qpid-cppAssignee: William Henry <whenry>
Status: CLOSED NOTABUG QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: urgent Docs Contact:
Priority: high    
Version: 1.2CC: gsim
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-18 19:47:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Log and tool output of the failure. none

Description William Henry 2009-06-16 15:59:53 UTC
Created attachment 348127 [details]
Log and tool output of the failure.

Description of problem:

[There is an attachment]


Both brokers in the cluster shutdown:

Broker 1:
2009-jun-16 09:14:30 error Error decoding events: framing-error: Framing version unsupported (qpid/framing/AMQFrame.cpp:113)
2009-jun-16 09:14:30 notice 192.168.2.14:11860(LEFT) leaving cluster TestCluster
2009-jun-16 09:14:30 notice Shut down

Broker 2:
2009-jun-16 09:14:30 error Error decoding events: framing-error: Framing version unsupported (qpid/framing/AMQFrame.cpp:113)
2009-jun-16 09:14:30 notice 192.168.2.15:11964(LEFT) leaving cluster TestCluster
2009-jun-16 09:14:30 notice Shut down

Version-Release number of selected component (if applicable):

1.1.2

How reproducible:

See attached file.


  
Actual results:


Expected results:


Additional info:

Comment 1 William Henry 2009-06-16 16:09:47 UTC
The customer is using 1.1.1 clients.  And I wonder if there are framing incompatibilities between 1.1.1 and 1.1.2  

Begs the question, if this is the problem, whether it's acceptable to have errata not compatible at the framing level.

Comment 2 Gordon Sim 2009-06-17 18:19:17 UTC
May have been solved by upgrading to correct openais version.

Comment 3 William Henry 2009-06-18 19:47:04 UTC
Solved by upgrading their openais version. Not a bug.