Red Hat Bugzilla – Bug 471307
Last value queue [RHEL4]
Last modified: 2009-02-04 11:16:26 EST
+++ This bug was initially created as a clone of Bug #452017 +++
Based on some message property, new messages 'overwrite' any previous message
with the same value for that property.
--- Additional comment from email@example.com on 2008-06-19 10:38:26 EDT ---
LVQ has the same basic features as a regular queue (such as acquire modes,
transactional delivery, ability to cluster, transient vs durable etc) and some
special features, described below. Elements in the queue can be represented as
one-dimensional array, where for a given identifier /routing key?/ there is only
one message. When a new message with the same identifier arrives, it replaces a
previous message with the same identifier. Sequence of the messages in the queue
does not matter. If it was possible to retrieve a specific message from this
logical queue, based on its identifier without retrieving other queue messages,
it would be even better.
--- Additional comment from firstname.lastname@example.org on 2008-10-08 15:36:44 EDT ---
details to use:
Manually validated on RHEL 5.2 / 4.7, i386 / x86_64 on packages
qpidd-0.4.725652-2.el5 using bz452017 comment #4 example code.
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.