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

Bug 552330

Summary: qpid-config from trunk causes exception in broker
Product: Red Hat Enterprise MRG Reporter: Tim Powers <timp>
Component: qpid-cppAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED ERRATA QA Contact: Martin Kudlej <mkudlej>
Severity: high Docs Contact:
Priority: low    
Version: 1.2CC: freznice, gsim, mkudlej
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, a broker would throw an exception when using 'qpid-config' from trunk. Note that previous revisions from trunk made the broker die immediately after the "Exception constructed" message. With this update, exception is no longer thrown and the broker works as expected.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-14 16:16:01 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:
Bug Depends On: 560978, 641330    
Bug Blocks:    
Attachments:
Description Flags
trace log from startup until the broker dies none

Description Tim Powers 2010-01-04 18:01:43 UTC 
Description of problem:
The broker will throw an exception when using the qpid-config from trunk.

Version-Release number of selected component (if applicable):
qpidc-0.5.752581-34.el5 and the qpid python bits from trunk (currently at svn revision 895618)

How reproducible:
Can reproduce every time.

Steps to Reproduce:
1. Start the broker
2. run `qpid-config -a amqs://servername`
  
Actual results:
The broker throws an exception. Note that previous revisions from trunk actually made the broker die immediately after the "Exception constructed" message. This was included in the broker's log file using the python bits at rev 895618: 

...
2010-jan-04 12:45:32 debug Credit allocated for 'rdest' on 0x2527648, was  bytes: 4294967295 msgs: 4294967295 now bytes: 4294967295 msgs: 4294967295
2010-jan-04 12:45:32 debug DeliveryRecord::setEnded() id=46
2010-jan-04 12:45:32 debug Exception constructed: Frame too large for buffer. (qpid/amqp_0_10/Connection.cpp:95)
2010-jan-04 12:45:32 error InternalErrorException: Frame too large for buffer. (qpid/amqp_0_10/Connection.cpp:95)

Expected results:
It should print out the current exchange/queue counts etc.

Additional info:
The broker is configured to use GSSAPI, SSL, and ACLs.
Comment 1 Gordon Sim 2010-01-04 21:49:06 UTC 
Should that be amqps://servername? With amqs://servername I can't reproduce the issue (qpid-config prints out stats and exits normally), using amqps (and hence ssl) I get a timeout error on the client. (rev 893315 for python client and qpid-config, qpidd-0.5.752581-34.el5 for broker).
Comment 2 Tim Powers 2010-01-05 09:53:45 UTC 
Yes, it's amqps://, I made a typo in the bug but it is what I uses. The client does timeout but the broker logs the error message I provided earlier.

I just tried it again and the broker started falling over again. FWIW, I have the following in qpidd.conf:

# Logging
log-to-syslog=0
log-to-file=/var/log/qpidd.log
log-time=1
log-level=1
log-enable=debug+

The last error logged before the broker dies is:
2010-jan-05 04:50:02 debug Exception constructed: Frame too large for buffer. (qpid/amqp_0_10/Connection.cpp:95)

And I get this:

# service qpidd status
qpidd dead but pid file exists
Comment 3 Tim Powers 2010-01-05 10:21:54 UTC 
I'm attaching the broker log (trace+) which includes everything from startup until the broker dies.
Comment 4 Tim Powers 2010-01-05 10:23:30 UTC 
Created attachment 381728 [details]
trace log from startup until the broker dies
Comment 5 Gordon Sim 2010-06-24 17:35:35 UTC 
This is the same root cause as https://bugzilla.redhat.com/show_bug.cgi?id=592861 and is fixed on 1.3.
Comment 7 Martin Kudlej 2010-10-08 13:03:04 UTC 
How can I reproduce this and with which versions of qpid-tools, please?
I cannot reproduce this with python-qpid-0.6.895736-1 and qpidd-0.5.752581-34(MRG 1.2). I found BZ641330 and there is also description of my verification/reproducing of this bug. Am I doing anything wrong?
Comment 8 Tim Powers 2010-10-08 13:18:48 UTC 
I wasn't using the python package. I was using a checkout from SVN.
Comment 9 Tim Powers 2010-10-08 13:20:59 UTC 
I forgot to mention that your python package isn't the same revision as what I was using anyway. 895618 was the revision for the checkout.
Comment 10 Martin Prpič 2010-10-10 08:05:10 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, a broker would throw an exception when using 'qpid-config' from trunk. Note that previous revisions from trunk made the broker die immediately after the "Exception constructed" message. With this update, exception is no longer thrown and the broker works as expected.
Comment 12 errata-xmlrpc 2010-10-14 16:16:01 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html