[
https://issues.apache.org/jira/browse/QPID-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156854#comment-13156854
]
Alex Rudyy commented on QPID-3640:
----------------------------------
Hi Rajith,
I fixed the setting of redelivery flag on 0-10 client as part of porting of
Dead Letter Queue and Max Delivery Count functionality (QPID-3642) from branch
to trunk.
The patch at
https://issues.apache.org/jira/secure/attachment/12505027/0002-QPID-3642-QPID-3640-Add-Dead-Letter-Queue-functional.patch
has the fix in it. However, it relies on changes made in a first patch at
https://issues.apache.org/jira/secure/attachment/12505026/0001-QPID-3642-QPID-3643-Add-Dead-Letter-Queue-functional.patch
.
Initially I have no intention to fix it but DLQ functionality depends on
redelivery flag being set correctly.
> When releasing msgs, the JMS client should not mark msgs in the prefetch
> buffer as "redelivered".
> -------------------------------------------------------------------------------------------------
>
> Key: QPID-3640
> URL: https://issues.apache.org/jira/browse/QPID-3640
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.10, 0.12
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.15
>
> Attachments: RecoveryTest.java
>
>
> When releasing messages, for ex when the application calls recover() or
> Connection.stop(), the client marks all messages in it's prefetch buffer as
> "redelivered". This is not correct, since messages in the prefetch buffer
> have not yet been seen (delivered) by the application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
