qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3562) the 0-10 client path does not act as expected with asynchronous consumers using a prefetch of 1 on transacted sessions
Date Thu, 17 Nov 2011 21:43:51 GMT

    [ https://issues.apache.org/jira/browse/QPID-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152359#comment-13152359
] 

Robbie Gemmell commented on QPID-3562:
--------------------------------------

I would probably have chosen to test prefetch=0 and preftech=1 in isolation rather than in
the same test, but it seems reasonable enough (I would consume 'Msg3' for completeness though).
The Javadoc mentions 3 more messages but the test sends 5 more. 

I dont think it covers this JIRA at all though, given the use of synchronous consumers and
the different handling of prefetch from onMessage that goes along with that being what prompted
the JIRA to be raised.
                
> 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:dev-subscribe@qpid.apache.org


Mime
View raw message