[
https://issues.apache.org/jira/browse/QPIDJMS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPIDJMS-382.
------------------------------------
Resolution: Fixed
> 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: [email protected]
For additional commands, e-mail: [email protected]
