[
https://issues.apache.org/jira/browse/PROTON-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559623#comment-16559623
]
ASF subversion and git services commented on PROTON-1901:
---------------------------------------------------------
Commit 2880325e013d9ef675fe61ea254d65a615558d15 in qpid-proton-j's branch
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=2880325 ]
PROTON-1901: fix handling of multiplexed incoming deliveries on a session,
check for various sequencing issues that would cause illegal states and knock
on problems
> arriving transfers for multiplexed multi-frame deliveries on a session are
> mishandled
> -------------------------------------------------------------------------------------
>
> Key: PROTON-1901
> URL: https://issues.apache.org/jira/browse/PROTON-1901
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: proton-j-0.27.2, proton-j-0.28.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Critical
> Fix For: proton-j-0.29.0
>
>
> If a session has a delivery arriving split into multiple transfer frames, and
> those frames are multiplexed with transfer[s] for other deliveries on the
> session (i.e there are multiple links on the session), then the transfer
> frames are mishandled.
> The handling in the transport session is essentially expecting a single
> outstanding delivery at a time, whereas the spec allows (and proton-j will in
> certain situations send) multiplexed deliveries for different links on a
> session. The mishandling can result in a transfer being incorrectly treated
> as the start of another delivery (potentially leaving earlier bits/ones
> incomplete) and/or merged with the wrong preceding transfer content.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
