It would be desirable to have improved logging from the broker when messages are expired from queues. The desired log message would include at least the queue name and message properties from the message being removed so that it is possible to debug any potential reason why a particular message expired. Additionally, the queue cleaner previously logged "Message expired from queue 'xyz'", but that functionality was removed during a recent refactor. Version-Release number of selected component (if applicable): Qpid 0.18
Created attachment 627709 [details] Proposed patch Moved logging of expired messages to a common function to support log filtering and dumped the message properties of the expired message.
Tested on RHEL5.9 and RHEL6.3 (both i386 and x86_64). The broker logs messages expiration and the log contains queue name from which the expired message was deleted along with message's properties. Packages used for testing: RHEL5.9 python-qpid-0.18-4.el5 python-qpid-qmf-0.18-9.el5 qpid-cpp-client-0.18-10.el5 qpid-cpp-client-devel-0.18-10.el5 qpid-cpp-server-0.18-10.el5 qpid-cpp-server-devel-0.18-10.el5 qpid-qmf-0.18-9.el5 qpid-tools-0.18-7.el5 RHEL6.3 python-qpid-0.18-4.el6.noarch python-qpid-qmf-0.18-9.el6_3.i686 qpid-cpp-client-0.18-10.el6_3.i686 qpid-cpp-client-devel-0.18-10.el6_3.i686 qpid-cpp-server-0.18-10.el6_3.i686 qpid-cpp-server-devel-0.18-10.el6_3.i686 qpid-qmf-0.18-9.el6_3.i686 qpid-tools-0.18-7.el6_3.noarch -> 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