Bug 813742
Summary: | queue replication fails when org.apache.qpid.example.Spout is used | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Pavel Moravec <pmoravec> |
Component: | qpid-cpp | Assignee: | Gordon Sim <gsim> |
Status: | CLOSED ERRATA | QA Contact: | Leonid Zhaldybin <lzhaldyb> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | esammons, gsim, jross, lzhaldyb, mcressma |
Target Milestone: | 2.3 | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qpid-cpp-0.18-1 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
The async queue replication code was setting frame flags incorrectly when there was an empty content frame (i.e. a content frame with content size equal to zero). This was incorrectly treated as not having a content frame at all so the end-of-frameset flag was incorrectly set on the header frame.
Consequence:
Such messages could not be replicated; the receiving broker would reject them as invalid AMQP.
Fix:
The end-of-frameset flag setting takes account of whether there is a content frame, even if it is empty.
Result:
Such messages are sent as valid AMQP frames and replicate as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-06 18:55:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pavel Moravec
2012-04-18 10:57:07 UTC
Fixed upstream: http://svn.apache.org/viewvc?rev=1327515&view=rev Also requires: http://svn.apache.org/viewvc?rev=1327596&view=rev for build on windows. Tested on RHEL5.8 and RHEL6.3 (both i386 and x86_64). The scenario from comment 0 works fine now with java clients. Packages used for testing: RHEL5 python-qpid-0.18-2.el5 python-qpid-qmf-0.18-2.el5 qpid-cpp-client-0.18-2.el5 qpid-cpp-client-devel-0.18-2.el5 qpid-cpp-client-devel-docs-0.18-2.el5 qpid-cpp-client-ssl-0.18-2.el5 qpid-cpp-server-0.18-2.el5 qpid-cpp-server-cluster-0.18-2.el5 qpid-cpp-server-devel-0.18-2.el5 qpid-cpp-server-ssl-0.18-2.el5 qpid-cpp-server-store-0.18-2.el5 qpid-cpp-server-xml-0.18-2.el5 qpid-java-client-0.18-3.el5 qpid-java-common-0.18-3.el5 qpid-java-example-0.18-3.el5 qpid-qmf-0.18-2.el5 qpid-qmf-devel-0.18-2.el5 qpid-tools-0.18-2.el5 RHEL6 python-qpid-0.18-2.el6_3 python-qpid-qmf-0.18-2.el6_3 qpid-cpp-client-0.18-2.el6_3 qpid-cpp-client-devel-0.18-2.el6_3 qpid-cpp-client-devel-docs-0.18-2.el6_3 qpid-cpp-server-0.18-2.el6_3 qpid-cpp-server-devel-0.18-2.el6_3 qpid-cpp-server-store-0.18-2.el6_3 qpid-cpp-server-xml-0.18-2.el6_3 qpid-java-client-0.18-3.el6 qpid-java-common-0.18-3.el6 qpid-java-example-0.18-3.el6 qpid-qmf-0.18-2.el6_3 qpid-tools-0.18-2.el6_3 -> VERIFIED 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 |