Bug 739941 - Unable to set message id using python spout
Summary: Unable to set message id using python spout
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid
Version: Development
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-20 14:04 UTC by Petr Matousek
Modified: 2025-02-10 03:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:14:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Matousek 2011-09-20 14:04:06 UTC
Description of problem:

Non-floating-point value cannot be used as message id, moreover message id is not correctly set using python spout.

Version-Release number of selected component (if applicable):
python-qpid-0.10-1

How reproducible:
100%

Steps to Reproduce:
1. qpid-config add queue q
2. spout -i 1-0 q
3. error regarding invalid floating-point value occurs
4. spout -i 1 q
5. drain q
6. message id of the consumed message does not correspond with the id submitted by the user in point 4

please see additional info for details.
  
Actual results:
Unable to set message id using python spout

Expected results:
Message id is handled correctly

Additional info:

The following code demonstrates that message id can not be set using python client, c++ client doesn't suffer from that.

# qpid-config add queue q
# $cppapi/spout -i 0-1 q
# $pyapi/spout -i 0-1 q
usage: spout [options] ADDRESS [ CONTENT ... ]

spout: error: option -i: invalid floating-point value: '0-1'
# $pyapi/spout -i 1 q
# $pyapi/drain q
Message(user_id='', correlation_id='', properties={'x-amqp-0-10.routing-key': u'q', u'spout-id': '0-1:0'}, content_type=u'')
Message(properties={'x-amqp-0-10.routing-key': u'q', u'spout-id': u'613b7f99-ca40-804f-b891-68bbffa39dd9:0'})

Comment 1 Red Hat Bugzilla 2025-02-10 03:14:14 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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