I.e. alter which log statements get emited without restarting the broker.
See also https://issues.apache.org/jira/browse/QPID-2966 upstream.
Fixed upstream by http://svn.apache.org/viewvc?rev=1044248&view=rev (http://svn.apache.org/viewvc?rev=1044308&view=rev provides extra check in automated test).
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: Sometimes it is useful to get finer grained logging to troubleshoot some problem, however the volume of logging that may be generated if left at that level can be burdensome. Consequence: There was previously no way to alter the log level without restarting the broker. This made troubleshooting and diagnosing issues harder. Change: A management method was added allowing the logging to be reconfigured at runtime without restarting the broker. Result: Can now turn up logging to investigate a problem and restore it to previous levels after the issue has been uncovered to prevent excessive logs.
The issue has been implemented Verified on RHEL4.9, RHEL5.6 and RHEL6.1, architectures: i386, x86_64 python-qpid-0.9.1079482-1.el5 python-qpid-qmf-0.9.1079953-3.el5 qpid-cpp-client-0.9.1079953-1.el5 qpid-cpp-client-devel-0.9.1079953-1.el5 qpid-cpp-client-devel-docs-0.9.1079953-1.el5 qpid-cpp-client-ssl-0.9.1079953-1.el5 qpid-cpp-mrg-debuginfo-0.9.1079953-1.el5 qpid-cpp-server-0.9.1079953-1.el5 qpid-cpp-server-cluster-0.9.1079953-1.el5 qpid-cpp-server-devel-0.9.1079953-1.el5 qpid-cpp-server-ssl-0.9.1079953-1.el5 qpid-cpp-server-store-0.9.1079953-1.el5 qpid-cpp-server-xml-0.9.1079953-1.el5 qpid-java-client-0.9.1080013-2.el5 qpid-java-common-0.9.1080013-2.el5 qpid-java-example-0.9.1080013-2.el5 qpid-qmf-0.9.1079953-3.el5 qpid-qmf-devel-0.9.1079953-3.el5 qpid-tools-0.9.1078967-1.el5 VERIFIED
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -8,4 +8,8 @@ A management method was added allowing the logging to be reconfigured at runtime without restarting the broker. Result: -Can now turn up logging to investigate a problem and restore it to previous levels after the issue has been uncovered to prevent excessive logs.+Can now turn up logging to investigate a problem and restore it to previous levels after the issue has been uncovered to prevent excessive logs. + +Release Note Entry: + +Previously, the level of logging being done could not be altered at runtime without restarting the broker. A management method is now used to allow the user to change the level of logging while the program run without requiring a restart. This allows users to get detailed logs during troubleshooting and return to normal logging settings to prevent excessive logs.
Technical note can be viewed in the release notes for 2.0 at the documentation stage here: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html-single/MRG_Release_Notes/index.html#tabl-MRG_Release_Notes-RHM_Update_Notes-RHM_Update_Notes
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/RHEA-2011-0890.html