You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2010/01/12 12:48:54 UTC

[jira] Created: (QPID-2338) [C++ Broker] Ring queue does not properly implement byte size limits for ring queues

[C++ Broker] Ring queue does not properly implement byte size limits for ring queues
------------------------------------------------------------------------------------

                 Key: QPID-2338
                 URL: https://issues.apache.org/jira/browse/QPID-2338
             Project: Qpid
          Issue Type: Bug
          Components: C++ Broker
    Affects Versions: 0.6
            Reporter: Rob Godfrey


To test I created a queue on the C++ broker with a size limit of 512 bytes, and a policy of "ring"

First I sent 5 messages each of size 100 bytes.
Then I sent a 6th 100 byte message - as expected this dequeued one of the existing messages

next I sent a single message of size 400 bytes
This caused only a single existing message to be dequeued, leading to 5 messages being enqueued with a total depth of 900 bytes (as reported by qpid-tool).  At this point I would have expected all but one of the existing messages to have been dequeued in order to make room for the 400 byte message

Finally I sent a single 1000 byte message.  This message in itself should have been too big for the queue, however it was enqueued; and only one 100 byte message was dequeued - leaving a total byte depth of 1800 bytes being enqueued.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] Updated: (QPID-2338) [C++ Broker] Ring queue does not properly implement byte size limits

Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey updated QPID-2338:
------------------------------

    Summary: [C++ Broker] Ring queue does not properly implement byte size limits  (was: [C++ Broker] Ring queue does not properly implement byte size limits for ring queues)

> [C++ Broker] Ring queue does not properly implement byte size limits
> --------------------------------------------------------------------
>
>                 Key: QPID-2338
>                 URL: https://issues.apache.org/jira/browse/QPID-2338
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.6
>            Reporter: Rob Godfrey
>            Assignee: Gordon Sim
>
> To test I created a queue on the C++ broker with a size limit of 512 bytes, and a policy of "ring"
> First I sent 5 messages each of size 100 bytes.
> Then I sent a 6th 100 byte message - as expected this dequeued one of the existing messages
> next I sent a single message of size 400 bytes
> This caused only a single existing message to be dequeued, leading to 5 messages being enqueued with a total depth of 900 bytes (as reported by qpid-tool).  At this point I would have expected all but one of the existing messages to have been dequeued in order to make room for the 400 byte message
> Finally I sent a single 1000 byte message.  This message in itself should have been too big for the queue, however it was enqueued; and only one 100 byte message was dequeued - leaving a total byte depth of 1800 bytes being enqueued.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] Assigned: (QPID-2338) [C++ Broker] Ring queue does not properly implement byte size limits for ring queues

Posted by "Gordon Sim (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gordon Sim reassigned QPID-2338:
--------------------------------

    Assignee: Gordon Sim

> [C++ Broker] Ring queue does not properly implement byte size limits for ring queues
> ------------------------------------------------------------------------------------
>
>                 Key: QPID-2338
>                 URL: https://issues.apache.org/jira/browse/QPID-2338
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.6
>            Reporter: Rob Godfrey
>            Assignee: Gordon Sim
>
> To test I created a queue on the C++ broker with a size limit of 512 bytes, and a policy of "ring"
> First I sent 5 messages each of size 100 bytes.
> Then I sent a 6th 100 byte message - as expected this dequeued one of the existing messages
> next I sent a single message of size 400 bytes
> This caused only a single existing message to be dequeued, leading to 5 messages being enqueued with a total depth of 900 bytes (as reported by qpid-tool).  At this point I would have expected all but one of the existing messages to have been dequeued in order to make room for the 400 byte message
> Finally I sent a single 1000 byte message.  This message in itself should have been too big for the queue, however it was enqueued; and only one 100 byte message was dequeued - leaving a total byte depth of 1800 bytes being enqueued.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org