You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2017/08/02 14:30:00 UTC
[jira] [Resolved] (PROTON-1525) enable configuring the initial
remote max frame size limit
[ https://issues.apache.org/jira/browse/PROTON-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved PROTON-1525.
------------------------------------
Resolution: Fixed
> enable configuring the initial remote max frame size limit
> ----------------------------------------------------------
>
> Key: PROTON-1525
> URL: https://issues.apache.org/jira/browse/PROTON-1525
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: proton-j-0.20.0
>
>
> Whilst trying to add support for the GSSAPI mechanism for QPIDJMS-303, Gary ran into an issue whereby the size of initial response lead to a sasl-init frame being emitted which fell foul of frame size enforcement at the receiver. Per the discussion on the mailing lists \[1\], this JIRA will add support for configurably relaxing this limit in scenerios it is known a larger value is necessary to allow an existing mechanism to function, by enabling control over the initial value of the transports remote max frame size before an Open is received.
> \[1\] https://lists.apache.org/thread.html/f5635f366dfcc757933537b472ee6b052f3a23dea9fdcc5f104983da@%3Cdev.qpid.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org