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

Bug 888449

Summary: Perl language bindings not properly mapping uint8_t type
Product: Red Hat Enterprise MRG Reporter: Darryl L. Pierce <dpierce>
Component: perl-qpidAssignee: Darryl L. Pierce <dpierce>
Status: CLOSED ERRATA QA Contact: Petra Svobodová <psvobodo>
Severity: medium Docs Contact:
Priority: medium    
Version: DevelopmentCC: freznice, iboverma, jross, lzhaldyb, pematous, psvobodo, tross
Target Milestone: 3.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: per-qpid-0.22-4.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 15:05:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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