Description of problem: Need to verify through a test that the acl reload function exposed through QMF is safe to use on an active broker. The test should have many clients doing random work on the broker with acl checks turned on. It should then periodically trigger reloading of the acl (no need to change it unless that would prevent reload actually occurring).
While testing this the broker core dumped. See 582366 for more details.
Created attachment 406598 [details] test case for testing the safety of acl reload. 1. Start the broker with the acl module and and --acl-file /tmp/policy.acl 2. The initial acl file should contain only "acl allow all all" 3. run the message_sender.py (This program will keep on publishing to amq.direct) 4. run acl_reloader.py with --mode allow | deny a few times
A fix has been put in place at rev 937120 in Qpid for bz 582366 I believe the reproducer attached here provides a good way to verify the safety of acl reloading.
verified on RHEL 5.5/4.8 - i386/x86_64: rpm -qa | grep -E '(qpid|ais|sesame)' | sort -n openais-0.80.6-16.el5_5.1 openais-debuginfo-0.80.6-16.el5_5.1 openais-devel-0.80.6-16.el5_5.1 python-qpid-0.7.946106-1.el5 qpid-cpp-client-0.7.946106-1.el5 qpid-cpp-client-devel-0.7.946106-1.el5 qpid-cpp-client-devel-docs-0.7.946106-1.el5 qpid-cpp-client-ssl-0.7.946106-1.el5 qpid-cpp-server-0.7.946106-1.el5 qpid-cpp-server-cluster-0.7.946106-1.el5 qpid-cpp-server-devel-0.7.946106-1.el5 qpid-cpp-server-ssl-0.7.946106-1.el5 qpid-cpp-server-store-0.7.946106-1.el5 qpid-cpp-server-xml-0.7.946106-1.el5 qpid-java-client-0.7.946106-3.el5 qpid-java-common-0.7.946106-3.el5 qpid-tools-0.7.946106-4.el5 rh-tests-distribution-MRG-Messaging-qpid_common-1.6-27 sesame-0.7.3918-2.el5 --> VERIFIED
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: The 'acl reload' function exposed through QMF is now safe to use on an active broker.
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. http://rhn.redhat.com/errata/RHSA-2010-0773.html