Bug 888449 - Perl language bindings not properly mapping uint8_t type
Summary: Perl language bindings not properly mapping uint8_t type
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: perl-qpid
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 3.0
: ---
Assignee: Darryl L. Pierce
QA Contact: Petra Svobodová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-18 18:11 UTC by Darryl L. Pierce
Modified: 2015-06-22 00:08 UTC (History)
7 users (show)

Fixed In Version: per-qpid-0.22-4.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-24 15:05:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-4507 0 None None None Never
Red Hat Product Errata RHEA-2014:1296 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 3.0 Release 2014-09-24 19:00:06 UTC

Description Darryl L. Pierce 2012-12-18 18:11:46 UTC
The language bindings only map specific between uint
{16,32,64}_t types and do not include the 8-bit uints.

Comment 2 Petr Matousek 2013-05-13 13:37:18 UTC
Due to this bug, the perl client is not able to query for the amqp message priority.

Current behavior:
The getPriority() message method returns the following value:
'_p_uint8_t=HASH(0x9f7850), it is not possible to get the uint8 value.

Expected behavior:
A number (8bit unsigned integer) is returned by the getPriority() message method.

QE Note: Please retest this issue as a part of this bz.

Comment 6 Petra Svobodová 2014-03-07 11:52:54 UTC
The patch with 8-bit uint type support was added; the message priority (8-bit uint value) is displayed properly now.

Verified on packages perl-qpid-0.22-7, qpid-cpp-0.22-35 on Rhel6.5-i386 and Rhel6.5-x86_64.

--> VERIFIED

Comment 7 errata-xmlrpc 2014-09-24 15:05:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1296.html


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