Bug 719589

Summary: Python example "server" fails
Product: Red Hat Enterprise MRG Reporter: Petra Svobodová <psvobodo>
Component: python-qpidAssignee: Ernie <eallen>
Status: CLOSED ERRATA QA Contact: mick <mgoulish>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: iboverma, jross, lzhaldyb, mgoulish, psvobodo
Target Milestone: 3.0Keywords: EasyFix, Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-qpid-0.22-3.el6, python-qpid-0.22-2.el5 Doc Type: Bug Fix
Doc Text:
It was discovered that the server example application referenced a non-existent `ReceiveError`, which caused the server example to crash upon start-up. The fix corrects the ReceiveError to ReceiverError, which allows the server example to operate as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 15:03:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Change ReceiveError exception to NotFound
none
The missing exception was ReceiverError (not ReceiveError or NotFound) none

Description Petra Svobodová 2011-07-07 12:30:58 UTC
Description of problem:
The "server" python example fails with message: "ReceiveError is not defined"; see Additional info part. 
The issue occurs in all supported operating systems (Rhel and Windows)

Version-Release number of selected component (if applicable):
[root@hostname api]# rpm -qa | grep qpid | sort
\python-qpid-0.10-1.el5
python-qpid-qmf-0.10-10.el5
qpid-cpp-client-0.10-8.el5
qpid-cpp-client-devel-0.10-8.el5
qpid-cpp-client-devel-docs-0.10-8.el5
qpid-cpp-client-rdma-0.10-8.el5
qpid-cpp-client-ssl-0.10-8.el5
qpid-cpp-server-0.10-8.el5
qpid-cpp-server-cluster-0.10-8.el5
qpid-cpp-server-devel-0.10-8.el5
qpid-cpp-server-rdma-0.10-8.el5
qpid-cpp-server-ssl-0.10-8.el5
qpid-cpp-server-store-0.10-8.el5
qpid-cpp-server-xml-0.10-8.el5
qpid-java-client-0.10-6.el5
qpid-java-common-0.10-6.el5
qpid-java-example-0.10-6.el5
qpid-qmf-0.10-10.el5
qpid-qmf-devel-0.10-10.el5
qpid-tests-0.7.946106-1.el5
qpid-tools-0.10-6.el5
ruby-qpid-0.7.946106-2.el5
ruby-qpid-qmf-0.10-10.el5

How reproducible:
100%

Steps to Reproduce:
1. Run the python "server" example.
  
Actual results:
The "server" application fails.

Expected results:
The "server" application should run.

Additional info:
See terminal transcript below:
[root@hostname api]# /usr/share/doc/python-qpid-0.10/examples/api/server "ADDR;{create:always}"
Traceback (most recent call last):
  File "/usr/share/doc/python-qpid-0.10/examples/api/server", line 90, in ?
    except ReceiveError, e:
NameError: name 'ReceiveError' is not defined

Comment 1 Ernie 2013-02-04 18:54:25 UTC
Created attachment 692955 [details]
Change ReceiveError exception to NotFound

The error being raised was a NotFound error.

Comment 2 Ernie 2013-02-21 20:24:51 UTC
Created attachment 700812 [details]
The missing exception was ReceiverError (not ReceiveError or NotFound)

Comment 3 Justin Ross 2013-04-18 14:38:29 UTC
http://svn.apache.org/viewvc?view=revision&revision=1469345

-> POST

Comment 4 mick 2013-07-11 13:47:07 UTC
To repro from source tree:

  cd trunk/qpid/python/examples/api
  ./server localhost:5672


what you see:

./server localhost:5672
Traceback (most recent call last):
  File "./server", line 90, in <module>
    except ReceiveError, e:
NameError: name 'ReceiveError' is not defined

Comment 5 mick 2013-07-11 15:01:00 UTC
sorry, comment 4 is wrong.

here's the way:

qpid-config add queue micks_new_queue
/usr/share/doc/python-qpid-0.22/examples/api/server micks_new_queue

Comment 6 mick 2013-07-12 19:43:05 UTC
On recent stable packages , I can't get this to reproduce -- original report said 100% repro on all architectures.


Am I doing something wrong, or has this one gone away?



Here is what I am doing:

    1. service qpidd start
    2. qpid-config add queue q-4-719589
    3. /usr/share/doc/python-qpid-0.18/examples/api/server  q-4-719589



MY OS is : RHEL 6.4 , x86_64



Here are my packages:

python-qpid-qmf-0.18-15.el6.x86_64
qpid-cpp-client-0.18-14.el6.x86_64
qpid-proton-c-0.4-2.2.el6.x86_64
python-saslwrapper-0.18-1.el6_3.x86_64
cyrus-sasl-devel-2.1.23-13.el6_3.1.x86_64
python-qpid-0.18-4.el6.noarch
qpid-cpp-server-0.18-14.el6.x86_64
cyrus-sasl-plain-2.1.23-13.el6_3.1.x86_64
qpid-proton-c-devel-0.4-2.2.el6.x86_64
saslwrapper-0.18-1.el6_3.x86_64
saslwrapper-devel-0.18-1.el6_3.x86_64
cyrus-sasl-gssapi-2.1.23-13.el6_3.1.x86_64
qpid-qmf-0.18-15.el6.x86_64
cyrus-sasl-md5-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-lib-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-2.1.23-13.el6_3.1.x86_64
qpid-tools-0.18-8.el6.noarch

Comment 7 mick 2013-07-22 14:52:28 UTC
Since I can't reproduce this on modern packages, I'm moving it to 'verified".

I understand that later, we may get a special category for bugs like this.

Comment 9 mick 2013-07-22 19:36:11 UTC
    OK, I *have* observed the bug under this condition:

      1. broker is not running.
      2. usr/share/doc/python-qpid-0.22/examples/api/server micks_new_queue

    bug result:

       except ReceiveError, e:
       NameError: name 'ReceiveError' is not defined


    However, I believe that the non-bug result is not that the server should run.
    The non-bug result is that the server should fail with a "Connection Refused" error.


    I observed bug result with latest-stable  (0.18) packages on RHEL 6.4 x86_64
    and observed my non-bug result on  RHEL 6.4 x ( x86_64 , i686 )

    so ... going back to verified.

Comment 12 errata-xmlrpc 2014-09-24 15:03:08 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