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

Robbie Gemmell updated QPIDJMS-464:
-----------------------------------
    Comment: was deleted

(was: Commit 60f4fe5911b0e0bee0e4b37a21d604fbab6ae91b in qpid-jms's branch 
refs/heads/master from Robert Gemmell
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=60f4fe5 ]

Revert "QPIDJMS-464: Update various test dependencies:"

This reverts commit 98b6bf8a7585141461ac60bc96d18838ae9dfe12.
)

> zero prefetch receive can hang if timeout reached whilst message is partially 
> transferred
> -----------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-464
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-464
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.43.0
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 0.44.0
>
>
> When a receive with timeout call is made using zero prefetch, the client 
> issues a credit, wait for a message to arrive, and if one doesn't in the 
> given time it drains the credit to either get a message or ensure there is 
> none and remove the credit. If the message is already partially transfered 
> (i.e it is likely larger, and typically multi-framed though it need not be) 
> at this point the client knows it doesnt need to drain, but the way it 
> handles this triggers a later mishandling of completing the receive request 
> when the message arrives.
> Some related comments can be found 
> [here|https://issues.apache.org/jira/browse/QPIDJMS-458?focusedCommentId=16872498&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16872498]
>  onwards.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to