[
https://issues.apache.org/jira/browse/QPID-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919493#comment-13919493
]
Pavel Moravec commented on QPID-5595:
-------------------------------------
I know there were some changes to LVQ around 0.14 - 0.18.
How do you create the queue? Could you try:
qpid-config add queue myLVQueue --lvq-key=qpid.subject
or use address string like:
"myLVQueue; {create:always, node:{ x-declare:{ arguments:{
'qpid.last_value_queue_key':'qpid.subject'}}}}"
> LVQ (Last Value Queue) not working
> ----------------------------------
>
> Key: QPID-5595
> URL: https://issues.apache.org/jira/browse/QPID-5595
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.22
> Environment: C++ broker, windows 7
> Reporter: Kathryn M Kowalski
>
> We are trying to upgrade from qpid version 0.10 to 0.22 with the broker
> running on Windows 7. Existing Python 2.7 code that makes use of last value
> queues is not working.
> Queue is setup with qpid.last_value_key = qpid.subject and this was verified
> with qpid_tool.
> Using 0.22, when the queue is bound to an exchange that is getting messages
> with one subject line and a heartbeat in the content the message depth
> continues to increase. Using 0.10 message depth stays a 1 or 0. If you
> drain the queue on the 0.22 broker all of the messages that should have been
> overwritten are still there.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
