qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathryn M Kowalski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-5595) LVQ (Last Value Queue) not working
Date Fri, 07 Mar 2014 20:30:43 GMT

    [ https://issues.apache.org/jira/browse/QPID-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924299#comment-13924299

Kathryn M Kowalski commented on QPID-5595:

Did some more experimentation - it is the addition of policy-type=ring that disables the LVQ
behavior.  (Unfortunately, the "durable" option I'm using on the queue kills the producer
in 0.22 - I see that has been fixed in 0.26 so we will have to upgrade to get a partial workaround)

> 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
>         Attachments: receive.py, send.py
> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message