You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2015/11/13 17:59:11 UTC

[jira] [Closed] (QPID-6841) [Java Broker] Calling recover on a subscription to a Sorted or Priority Queue may cause messages to become stuck

     [ https://issues.apache.org/jira/browse/QPID-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall closed QPID-6841.
----------------------------

> [Java Broker] Calling recover on a subscription to a Sorted or Priority Queue may cause messages to become stuck
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6841
>                 URL: https://issues.apache.org/jira/browse/QPID-6841
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.28, 0.30, 0.32
>            Reporter: Rob Godfrey
>            Assignee: Keith Wall
>             Fix For: qpid-java-6.0
>
>
> When recover is called, the messages are delivered to the consumer, this is updating the lastSeenEntry of the consumer with each recovered message in turn - this is incorrect behaviour.  If a new message comes in while the last seen is "before" the new message then the recovery sets the last seen to a message "after" the last seen, then the consumer will not see the new message unless a later message comes in which is "before" the stuck message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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