You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/11/07 20:38:00 UTC
[jira] [Commented] (PROTON-2649) Client sender could get stalled when multiple senders in single session use outgoing capacity limits
[ https://issues.apache.org/jira/browse/PROTON-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630020#comment-17630020 ]
ASF subversion and git services commented on PROTON-2649:
---------------------------------------------------------
Commit ab43220acf92d14d3a41fb21e1f668edd7c4c43a in qpid-proton-dotnet's branch refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=qpid-proton-dotnet.git;h=ab43220 ]
PROTON-2649 Update sender sendable state on check to reflect state
When a sender is asked if it is sendable update the state if the session
capacity reports that it is not available while the sender link does
still have credit. This allows the engine to notifity all senders in
the not sendable state that they have recovered.
> Client sender could get stalled when multiple senders in single session use outgoing capacity limits
> ----------------------------------------------------------------------------------------------------
>
> Key: PROTON-2649
> URL: https://issues.apache.org/jira/browse/PROTON-2649
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-dotnet
> Affects Versions: proton-dotnet-1.0.0-M5
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Major
> Fix For: proton-dotnet-1.0.0-M6
>
>
> Senders in single session competing for outgoing capacity could get stuck awaiting an update event indicating that credit to send has been restored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org