Red Hat Bugzilla – Bug 487500
LVQ does not persist durable messages
Last modified: 2015-11-15 19:06:51 EST
Created attachment 333314 [details]
Patch for qpidd to support persisted LVQ (Warning: this still has open issues)
Attached test shows a recovery problem with this patch that has yet to be addressed.
Created attachment 333315 [details]
This contains a test for persistence and recovery of messages in an LVQ. There is one outstadning issue causing it to fail at present.
Fixed in r748214. Test case added to stores persistence.py (r3138). To test just use persistent messages on an LVQ.
I have added --durable and --lvq-match-value options to the sender test utility in the qpid svn. These can be used to do some testing of this issue. E.g.
1. create a durable LVQ queue:
qpid-config --durable --order lvq add queue test-queue
2. send some durable messages:
for m in one two three; do echo $m; done | ./src/tests/sender --lvq-match-value aaa --durable true
3. restart broker
4. check the correct set of messages are delivered. E.g. for simple case above:
Created attachment 333366 [details]
empty file (how do I delete attachments?!)
The issue has been fixed, validated on RHEL 4.7 / 5.2 / 5.3 i386 / x86_64 on packages: qpidd-0.5.752581-1.el4/5.
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.