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 2018/04/23 18:34:00 UTC
[jira] [Commented] (QPIDJMS-382) limit outgoing frame sizes to
configured maxFrameSize
[ https://issues.apache.org/jira/browse/QPIDJMS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448661#comment-16448661 ]
ASF subversion and git services commented on QPIDJMS-382:
---------------------------------------------------------
Commit 8f876f9260c131c00d68181acf53f1110fca802b in qpid-jms's branch refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=8f876f9 ]
QPIDJMS-382: limit outgoing transfers to at most the connections configured maxFrameSize
> limit outgoing frame sizes to configured maxFrameSize
> -----------------------------------------------------
>
> Key: QPIDJMS-382
> URL: https://issues.apache.org/jira/browse/QPIDJMS-382
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 0.32.0
>
>
> Previously, we (or rather, proton-j) would send the largest frames possible given the peers advertised maxFrameSize, even where this significantly exceeds the maxFrameSize we have advertised to the peer, potentially resulting in larger memory use and lower perf than desired. PROTON-1828 added ability to limit outgoing frame size, we should use this to govern outgoing frame sizes to at most the client connections configured maxFrameSize.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org