[
https://issues.apache.org/jira/browse/QPID-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-3562.
----------------------------------
Resolution: Fixed
Completion sending moved to postDeliver, and in addition to previous
restrictions only occurs if the transaction wasnt committed (in the
asynchronous delivery case).
> the 0-10 client path does not act as expected with asynchronous consumers
> using a prefetch of 1 on transacted sessions
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3562
> URL: https://issues.apache.org/jira/browse/QPID-3562
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.12
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.13
>
>
> the 0-10 client path does not act as expected with asynchronous consumers
> using a prefetch of 1 on transacted sessions, as the client is able to hold a
> 2nd message during processing of a slow onMessage handler. This is because
> completions are sent to ensure credit does not dry up, allowing a
> large-than-prefetch number of messages to be consume in a given transaction.
> However, this is done prior to delivery to the client application, which
> causes the client to get sent a 2nd message by the broker.
> This should isntead occur after delivery has completed (if it is necessary:
> the client may have committed, which sends accepting completions anyway) to
> give the expected behaviour.
--
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]
