Bug 856299 - Sender.send(timeout=N) should pass timeout=N to self.sync()
Summary: Sender.send(timeout=N) should pass timeout=N to self.sync()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid
Version: 2.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 2.3
: ---
Assignee: Ernie
QA Contact: Frantisek Reznicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-11 16:58 UTC by Justin Ross
Modified: 2015-11-16 01:14 UTC (History)
6 users (show)

Fixed In Version: python-qpid-0.18-4
Doc Type: Bug Fix
Doc Text:
Cause: Send a messaging using sender.send(<timeoutvalue>) Consequence: Occasionally takes longer than <timeoutvalue> to return from the send call Fix: Added missing timeout value to sync() call Result: Sending a message will not pause for longer than the passed timeout value.
Clone Of:
Environment:
Last Closed: 2013-03-06 18:51:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
add the timeout=timeout argument to self.sync() (352 bytes, patch)
2012-10-12 17:08 UTC, Ernie 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-4102 0 None None None 2012-10-17 21:54:48 UTC
Red Hat Product Errata RHSA-2013:0561 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging 2.3 security update 2013-03-06 23:48:13 UTC

Description Justin Ross 2012-09-11 16:58:07 UTC 
See https://issues.apache.org/jira/browse/QPID-4102
Comment 3 Ernie 2012-10-12 17:08:25 UTC 
Created attachment 626132 [details]
add the timeout=timeout argument to self.sync()

Patch approved by Rafi
Comment 7 Justin Ross 2012-10-17 21:54:48 UTC 
Fixed upstream on trunk at revision 1399445. -> POST.
Comment 10 Frantisek Reznicek 2012-11-06 11:50:37 UTC 
The issue has been resolved, sender now correctly passes timeout argument to session.sync(timeout=) call.

Tested on RHEL 5.9 beta / 6.3 i386 / x86_64 on packages:
# rpm -qa | grep qpid | sort
python-qpid-0.18-4.el5
python-qpid-qmf-0.18-5.el5
qpid-cpp-client-0.18-6.el5
qpid-cpp-client-devel-0.18-6.el5
qpid-cpp-client-devel-docs-0.18-6.el5
qpid-cpp-client-rdma-0.18-6.el5
qpid-cpp-client-ssl-0.18-6.el5
qpid-cpp-server-0.18-6.el5
qpid-cpp-server-cluster-0.18-6.el5
qpid-cpp-server-devel-0.18-6.el5
qpid-cpp-server-rdma-0.18-6.el5
qpid-cpp-server-ssl-0.18-6.el5
qpid-cpp-server-store-0.18-6.el5
qpid-cpp-server-xml-0.18-6.el5
qpid-java-client-0.18-4.el5
qpid-java-common-0.18-4.el5
qpid-java-example-0.18-4.el5
qpid-jca-0.18-4.el5
qpid-jca-xarecovery-0.18-4.el5
qpid-jca-zip-0.18-4.el5
qpid-qmf-0.18-5.el5
qpid-qmf-devel-0.18-5.el5
qpid-tests-0.18-1.el5
qpid-tools-0.18-4.el5
rh-qpid-cpp-tests-0.18-6.el5
ruby-qpid-qmf-0.18-5.el5


-> VERIFIED
Comment 12 errata-xmlrpc 2013-03-06 18:51:56 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/RHSA-2013-0561.html
Note You need to log in before you can comment on or make changes to this bug.