Bug 1011902 - [AMQP 1.0] qpidd crashes if attempting to use QMF over AMQP 1.0
Summary: [AMQP 1.0] qpidd crashes if attempting to use QMF over AMQP 1.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 3.0
: ---
Assignee: Gordon Sim
QA Contact: Petr Matousek
URL:
Whiteboard:
Depends On:
Blocks: 1010399
TreeView+ depends on / blocked
 
Reported: 2013-09-25 11:12 UTC by Gordon Sim
Modified: 2015-01-21 12:56 UTC (History)
5 users (show)

Fixed In Version: qpid-cpp-0.22-17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-21 12:56:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
An example that uses QMFv2 over 1.0 to retrieve a list of queues from broker (2.34 KB, text/x-c++src)
2013-09-25 11:12 UTC, Gordon Sim 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-5150 0 None None None Never

Description Gordon Sim 2013-09-25 11:12:26 UTC 
Created attachment 802735 [details]
An example that uses QMFv2 over 1.0 to retrieve a list of queues from broker

Description of problem:

The QMF code in the broker assumes message have arrived in 0-10 format. If they are in fact 1.0 messages it segfaults.

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

qpid 0.24

How reproducible:

100%

Steps to Reproduce:
1. run attached example against a 1.0 enabled qpidd

Actual results:

broker seg faults

Expected results:

broker shouldn't seg fault (ideally the example should return a list of queues)

Additional info:
Comment 1 Gordon Sim 2013-09-25 11:28:44 UTC 
Fixed upstream by https://svn.apache.org/r1525044 and https://svn.apache.org/r1526156
Comment 4 Petr Matousek 2014-01-09 14:21:26 UTC 
This issue has been fixed. Verified on rhel6.5 (x86_64, i386).

packages under test:
qpid-cpp-*-0.22-30

-> VERIFIED
Note You need to log in before you can comment on or make changes to this bug.