You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2009/11/17 16:01:40 UTC

[jira] Created: (QPID-2209) FailedDequeueException whilst clearing queue of messages moved/copied from another queue

FailedDequeueException whilst clearing queue of messages moved/copied from another queue
----------------------------------------------------------------------------------------

                 Key: QPID-2209
                 URL: https://issues.apache.org/jira/browse/QPID-2209
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker, Java Management : JMX Interface
    Affects Versions: 0.5
            Reporter: Robbie Gemmell
            Priority: Minor
             Fix For: 0.6


Whilst testing the updated management console, attempt was made to clear the queues used previously as destinations to test copying and moving messages between queues. The originating queue had previously been cleared without issue, however attempting to clear the queues to which the messages were moved/copied resulted in a FailedDequeueException. 

This may relate to a difference in treatment of persistent messages between their initial delivery to the broker, and when they are moved/copied. Currently all persistent messages are entered into the store on arrival at the broker, regardless of whether the queue they are destined for is durable. When moving/copying, the queue durability is also checke, and so the messages that threw the FailedDequeueException (but apprently were dequeued) had not been entered into the store for the destination queue as the queue was not durable.

-- 
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-2209) FailedDequeueException whilst clearing queue of messages moved/copied from another queue

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

Robbie Gemmell updated QPID-2209:
---------------------------------

    Status: Ready To Review  (was: In Progress)

> FailedDequeueException whilst clearing queue of messages moved/copied from another queue
> ----------------------------------------------------------------------------------------
>
>                 Key: QPID-2209
>                 URL: https://issues.apache.org/jira/browse/QPID-2209
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Management : JMX Interface
>    Affects Versions: 0.5
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.6
>
>
> Whilst testing the updated management console, attempt was made to clear the queues used previously as destinations to test copying and moving messages between queues. The originating queue had previously been cleared without issue, however attempting to clear the queues to which the messages were moved/copied resulted in a FailedDequeueException. 
> This may relate to a difference in treatment of persistent messages between their initial delivery to the broker, and when they are moved/copied. Currently all persistent messages are entered into the store on arrival at the broker, regardless of whether the queue they are destined for is durable. When moving/copying, the queue durability is also checke, and so the messages that threw the FailedDequeueException (but apprently were dequeued) had not been entered into the store for the destination queue as the queue was not durable.

-- 
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-2209) FailedDequeueException whilst clearing queue of messages moved/copied from another queue

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

Robbie Gemmell updated QPID-2209:
---------------------------------

    Fix Version/s:     (was: 0.6)
                   0.7

Moving to 0.7. Issue may no longer exist on trunk following recent updates in this area (but does on 0.5.x-dev), needs investigation.

> FailedDequeueException whilst clearing queue of messages moved/copied from another queue
> ----------------------------------------------------------------------------------------
>
>                 Key: QPID-2209
>                 URL: https://issues.apache.org/jira/browse/QPID-2209
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Management : JMX Interface
>    Affects Versions: 0.5
>            Reporter: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.7
>
>
> Whilst testing the updated management console, attempt was made to clear the queues used previously as destinations to test copying and moving messages between queues. The originating queue had previously been cleared without issue, however attempting to clear the queues to which the messages were moved/copied resulted in a FailedDequeueException. 
> This may relate to a difference in treatment of persistent messages between their initial delivery to the broker, and when they are moved/copied. Currently all persistent messages are entered into the store on arrival at the broker, regardless of whether the queue they are destined for is durable. When moving/copying, the queue durability is also checke, and so the messages that threw the FailedDequeueException (but apprently were dequeued) had not been entered into the store for the destination queue as the queue was not durable.

-- 
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-2209) FailedDequeueException whilst clearing queue of messages moved/copied from another queue

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

Robbie Gemmell updated QPID-2209:
---------------------------------

    Fix Version/s:     (was: 0.7)
                   0.6
         Assignee: Robbie Gemmell

This issue has been resolved on trunk through previous changes. Fix applied for 0.5.x-dev branch to bring move/copy message persistence checks in line with the rest of the broker.

> FailedDequeueException whilst clearing queue of messages moved/copied from another queue
> ----------------------------------------------------------------------------------------
>
>                 Key: QPID-2209
>                 URL: https://issues.apache.org/jira/browse/QPID-2209
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Management : JMX Interface
>    Affects Versions: 0.5
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.6
>
>
> Whilst testing the updated management console, attempt was made to clear the queues used previously as destinations to test copying and moving messages between queues. The originating queue had previously been cleared without issue, however attempting to clear the queues to which the messages were moved/copied resulted in a FailedDequeueException. 
> This may relate to a difference in treatment of persistent messages between their initial delivery to the broker, and when they are moved/copied. Currently all persistent messages are entered into the store on arrival at the broker, regardless of whether the queue they are destined for is durable. When moving/copying, the queue durability is also checke, and so the messages that threw the FailedDequeueException (but apprently were dequeued) had not been entered into the store for the destination queue as the queue was not durable.

-- 
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