Bug 1009422 - consumed text message content is always <void> when using drain example
Summary: consumed text message content is always <void> when using drain example
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: 3.0
: ---
Assignee: Gordon Sim
QA Contact: Petr Matousek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-18 12:14 UTC by Petr Matousek
Modified: 2015-01-21 12:57 UTC (History)
4 users (show)

Fixed In Version: qpid-cpp-0.22-16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


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

Description Petr Matousek 2013-09-18 12:14:19 UTC
Description of problem:

Following change was done between qpid-cpp-client-devel-0.22-13 and
qpid-cpp-client-devel-0.22-14 in drain client:
<                     std::cout << message.getContent();
---
>                     std::cout << message.getContentObject();

As the content object is not filled by spout on sending a text message, the getContentObject() call always returns <void>.

Note: sending ie.: mapMessage do not suffer from that (spout correctly fills the content object)

Version-Release number of selected component (if applicable):
qpid-cpp-*-0.22-14

How reproducible:
100%

Steps to Reproduce:
1. drain -f amq.direct
2. spout --content "textMessage" amq.direct
3. the consumed message content is <void>

Actual results:
Consumed message content is always <void>

Expected results:
Consumed message content is properly displayed

Additional info:
./drain -f amq.direct
Message(properties={spout-id:efee0070-658e-4e7d-a3ff-5d4f0c700130:0, x-amqp-0-10.routing-key:}, content='<void>')

Comment 2 Gordon Sim 2013-09-18 19:24:58 UTC
Fixed upstream: https://svn.apache.org/r1524505

Comment 4 Petr Matousek 2013-10-25 09:23:27 UTC
This issue has been fixed. Verified on rhel6.4 (i386, x86_64).

packages used for testing:
qpid-cpp-*-0.22-22.el6


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