Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
qpid-python-1.35.0
-
None
Description
The python test qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message for 0.9 AMQP protocol fails occasionally with the following stack trace:
qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message (from (TEST-python_pre1.0.xml)) Failing for the past 1 build (Since Failed#1256 ) Took 14 sec. Stacktrace Error during test: Traceback (most recent call last): File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/bin/qpid-python-test", line 340, in run phase() File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py", line 45, in test_largest_single_frame_message self.echo_message(body) File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py", line 61, in echo_message msg = consumer.get(timeout=1) File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid/queue.py", line 51, in get result = BaseQueue.get(self, block, timeout) File "/usr/lib/python2.7/Queue.py", line 176, in get raise Empty Empty
The client and broker logs have records of the message being received by the client in timely manner (It took 3millisecond to deliver the message). However, the received message was not put into the client queue and test failed.
It is unclear at the moment whether it is an issue with threads or a bug in client code. More investigation is required.
The issue might cause sporadic timeouts in applications using 0.8...0.91 python API.