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

ASF subversion and git services commented on QPIDJMS-112:
---------------------------------------------------------

Commit bdadbb61db8df98dee1a56e556b8187fc65e1306 in qpid-jms's branch 
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=bdadbb6 ]

QPIDJMS-112: updates to make zero prefetch consumers doing receive() with no 
timeout wait for the 'pull' operation to complete, allowing the failover layer 
to handle that situation itself


> have receiveNoWait and receive(timeout) drain credit to ensure no message is 
> available
> --------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-112
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-112
>             Project: Qpid JMS
>          Issue Type: Improvement
>          Components: qpid-jms-client
>    Affects Versions: 0.5.0
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>             Fix For: 0.6.0
>
>
> As of QPIDJMS-92, if the consumer has been configured to have no prefetch, 
> the client will issue and drain a single credit before inspecting its local 
> message queue, ensuring that any available message sent by a broker will be 
> returned to the application. However, if the client has prefetch, the 
> consumer credit is granted and never drained, which means that a 
> recieveNoWait call will only return a message if first given time to prefetch 
> it, otherwise returning null even where messages 'are available'.
> The behaviour should be updated such that if no message is locally available 
> when checked, the credit is drained to ensure messages available on the 
> broker are retrieved and given the chance to be returned rather than 
> returning null.
> The same improvement can be applied to receive with a timeout to give 
> behaviour many would expect where messages 'are available', though it might 
> additionally be useful if the drain could be disabled in this case.



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

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

Reply via email to