Hide Forgot
Description of problem: Brokers in the cluster during failover scenario between two machines 6.2 one i686 second x86_64. This error does not cause fatal condition. 2011-12-01 10:42:28 info Queue "test_cluster_failover_1to1_mq_0": Policy created: type=reject; maxCount=0; maxSize=104857600 2011-12-01 10:42:28 info Queue "test_cluster_failover_1to1_mq_0": Flow limit created: flowStopCount=0, flowResumeCount=0, flowStopSize=83886080, flowResumeSize=73400320 2011-12-01 10:42:29 error Detected two management objects with the same identifier: 0-126-1--733(org.apache.qpid.broker:queue:test_cluster_failover_1to1_mq_0) ... Version-Release number of selected component (if applicable): cman-3.0.12.1-23.el6.i686 corosync-1.4.1-4.el6.i686 corosynclib-1.4.1-4.el6.i686 corosynclib-devel-1.4.1-4.el6.i686 openais-1.1.1-7.el6.i686 openaislib-1.1.1-7.el6.i686 python-qpid-0.12-1.el6.noarch python-qpid-qmf-0.12-6.el6.i686 python-saslwrapper-0.10-2.el6.i686 qpid-cpp-client-0.12-6.el6.i686 qpid-cpp-client-devel-0.12-6.el6.i686 qpid-cpp-client-rdma-0.12-6.el6.i686 qpid-cpp-client-ssl-0.12-6.el6.i686 qpid-cpp-debuginfo-0.12-6.el6.i686 qpid-cpp-server-0.12-6.el6.i686 qpid-cpp-server-cluster-0.12-6.el6.i686 qpid-cpp-server-devel-0.12-6.el6.i686 qpid-cpp-server-rdma-0.12-6.el6.i686 qpid-cpp-server-ssl-0.12-6.el6.i686 qpid-cpp-server-store-0.12-6.el6.i686 qpid-cpp-server-xml-0.12-6.el6.i686 qpid-java-client-0.10-11.el6.noarch qpid-java-common-0.10-11.el6.noarch qpid-java-example-0.10-11.el6.noarch qpid-java-jca-0.10-11.el6.noarch qpid-java-jca-zip-0.10-11.el6.noarch qpid-qmf-0.12-6.el6.i686 qpid-qmf-debuginfo-0.12-6.el6.i686 qpid-qmf-devel-0.12-6.el6.i686 qpid-tests-0.12-1.el6.noarch qpid-tools-0.12-2.el6.noarch rgmanager-3.0.12.1-5.el6.i686 rh-qpid-cpp-tests-0.12-6.el6.i686 ruby-qpid-0.7.946106-2.el6.i686 ruby-qpid-qmf-0.12-6.el6.i686 ruby-saslwrapper-0.10-2.el6.i686 How reproducible: 80% Steps to Reproduce: 1. ./ctests.py --qmf-data-timeout=200 --cluster-maximize-uptime <host-A> <host-B> --selinux-state-force=0 --log-to-file=a.log --exec-tests=testset_cluster_failover --testset-loop-cnt=5 2. look in *qpidd.log in pwd or in machines /var/lib/qpidd/qpidd.log Actual results: Detected identifier belonging to two management objects. Expected results: Every management object should have unique identifier. Additional info:
This issue is still reproducible even on qpid in new HA: 2014-03-14 14:56:16 [Management] error Detected two management objects with the same identifier: 0-2502-1--581053(org.apache.qpid.broker:queue:test_a1_c1_mcL_msL_md0_txrxkillN_sigterm_brks_00) on packages: perl-qpid-0.22-11.el6.x86_64 perl-qpid-debuginfo-0.22-11.el6.x86_64 python-qpid-0.22-12.el6.noarch python-qpid-qmf-0.22-28.el6.x86_64 qpid-cpp-client-0.22-36.el6.x86_64 qpid-cpp-client-devel-0.22-36.el6.x86_64 qpid-cpp-client-devel-docs-0.22-36.el6.noarch qpid-cpp-client-rdma-0.22-36.el6.x86_64 qpid-cpp-debuginfo-0.22-36.el6.x86_64 qpid-cpp-server-0.22-36.el6.x86_64 qpid-cpp-server-devel-0.22-36.el6.x86_64 qpid-cpp-server-ha-0.22-36.el6.x86_64 qpid-cpp-server-linearstore-0.22-36.el6.x86_64 qpid-cpp-server-rdma-0.22-36.el6.x86_64 qpid-cpp-server-xml-0.22-36.el6.x86_64 qpid-java-client-0.22-6.el6.noarch qpid-java-common-0.22-6.el6.noarch qpid-java-example-0.22-6.el6.noarch qpid-jca-0.22-2.el6.noarch qpid-jca-xarecovery-0.22-2.el6.noarch qpid-jca-zip-0.22-2.el6.noarch qpid-proton-c-0.6-1.el6.x86_64 qpid-proton-c-devel-0.6-1.el6.x86_64 qpid-proton-debuginfo-0.6-1.el6.x86_64 qpid-qmf-0.22-28.el6.x86_64 qpid-qmf-debuginfo-0.22-28.el6.x86_64 qpid-qmf-devel-0.22-28.el6.x86_64 qpid-snmpd-1.0.0-16.el6.x86_64 qpid-snmpd-debuginfo-1.0.0-16.el6.x86_64 qpid-tools-0.22-9.el6.noarch rh-qpid-cpp-tests-0.22-36.el6.x86_64