Red Hat Bugzilla – Bug 461816
Broker sends message.transfer after sending a session.detach
Last modified: 2009-02-04 10:35:17 EST
It should not send anything after the detach (or indeed after the execution.exception).
Also tracked by https://issues.apache.org/jira/browse/QPID-1413
Created attachment 322765 [details]
This is quite hard to observe from an application. I was discovered when using the python client and the attached application emulates that use case. As the channel is reused, transfers that arrive after the detach is sent cause problems for the subsequently attached sessions.
The failure exhibits itself when running this test app by something like the following:
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python2.4/threading.py", line 442, in __bootstrap
File "/usr/lib/python2.4/threading.py", line 422, in run
File "/home/gordon/qpid/trunk/qpid/python/qpid/connection.py", line 175, in run
File "/home/gordon/qpid/trunk/qpid/python/qpid/delegates.py", line 50, in received
File "/home/gordon/qpid/trunk/qpid/python/qpid/session.py", line 220, in received
File "/home/gordon/qpid/trunk/qpid/python/qpid/session.py", line 280, in received
Fixed by r711931. Attached test case runs without error.
Created attachment 323058 [details]
qpid_test_msg_trasfer_after_session_detach_bz461816 failing test
RHTS test qpid_test_msg_trasfer_after_session_detach_bz461816 almost finished.
The result of the test shows that issue is not gone.
See attached current state of test including logfile (python core test logfile & qpidd trace log)
See common_transcript lines 9173-9188.
Observed on RHEL5.2 x86_64, qpidd-0.3.711915-2.el5, rhm-0.2.2694-1.el5
RHTS test qpid_test_msg_trasfer_after_session_detach_bz461816 updated and qpidd version updated to revision > 711931.
Test passing on multiple machines (RHEL4.7/5.2 i386/x86_64).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.