Red Hat Bugzilla – Bug 727182
Support DTX transactions in a cluster.
Last modified: 2015-11-15 20:13:37 EST
Description of problem: Broker currently does not support DTX transactions. It raises an exception if there is an attempt to create one. Add support for DTX, with appropriate testing for cluster cases. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: qpid-txtest --dtx yes Actual results: Transfering from tx-test-1 to tx-test-2 Transfering from tx-test-2 to tx-test-1 2011-08-01 09:38:45 warning Broker closed connection: 501, DTX transactions are not currently supported by cluster. Transfer interrupted: framing-error: DTX transactions are not currently supported by cluster. 2011-08-01 09:38:45 warning Broker closed connection: 501, DTX transactions are not currently supported by cluster. Transfer interrupted: framing-error: DTX transactions are not currently supported by cluster. 2011-08-01 09:38:45 warning Broker closed connection: 501, DTX transactions are not currently supported by cluster. framing-error: DTX transactions are not currently supported by cluster. Expected results: The test should pass.
Note above should read _clustered_ broker does not support DTX.
This bug is fixed on upstream trunk as of r1163347. The fix includes: r1161742 | QPID-3384: Enable DTX transactions in a cluster. r1162092 | QPID-3384: Fix compilation errors for boost 1.39 and gcc 4.4.4 r1162104 | QPID-3384: Fix cmake build (added missing file to list) r1163347 | QPID-3384: DTX transactions - replicate suspended transactions.
*** Bug 705490 has been marked as a duplicate of this bug. ***
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: DTX transactions were disabled in a cluster. Consequence: Attempting to create a DTX transaction failed with an "unsupported" error. Fix: DTX transactions are now enabled. Result: You can use DTX transactions in a cluster.
Distributed transactions added and functional as proved by small test. Longer stress test started to prove feature stability.
Extensive testing on RHEL5.7 / 6.2 clusters finished and proved that functionality is enabled, but not robust yet. There was detected transaction integrity issue - bug 772166 which should be solved before. Added defect dependency.
The functionality was implemented, tested on RHEL 5.7 / 6.2 i386 / x86_64 on packages: openais-0.80.6-30.el5_7.4 python-qpid-0.14-1.el5 python-qpid-qmf-0.14-2.el5 python-saslwrapper-0.10-4.el5 qpid-cpp-client-0.14-3.el5 qpid-cpp-client-devel-0.14-3.el5 qpid-cpp-client-devel-docs-0.14-3.el5 qpid-cpp-client-rdma-0.14-3.el5 qpid-cpp-client-ssl-0.14-3.el5 qpid-cpp-mrg-debuginfo-0.14-3.el5 qpid-cpp-server-0.14-3.el5 qpid-cpp-server-cluster-0.14-3.el5 qpid-cpp-server-devel-0.14-3.el5 qpid-cpp-server-rdma-0.14-3.el5 qpid-cpp-server-ssl-0.14-3.el5 qpid-cpp-server-store-0.14-3.el5 qpid-cpp-server-xml-0.14-3.el5 qpid-java-client-0.14-1.el5 qpid-java-common-0.14-1.el5 qpid-java-example-0.14-1.el5 qpid-qmf-0.14-2.el5 qpid-qmf-debuginfo-0.14-2.el5 qpid-qmf-devel-0.14-2.el5 qpid-tests-0.14-1.el5 qpid-tools-0.14-1.el5 rh-qpid-cpp-tests-0.14-3.el5 ruby-qpid-qmf-0.14-2.el5 ruby-saslwrapper-0.10-4.el5 saslwrapper-0.10-4.el5 saslwrapper-debuginfo-0.10-4.el5 saslwrapper-devel-0.10-4.el5 sesame-1.0-2.el5 sesame-debuginfo-1.0-2.el5 -> VERIFIED Note: bug 772166 dependency was removed and will be solved separately
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-2012-0529.html