[
https://issues.apache.org/jira/browse/DISPATCH-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542646#comment-15542646
]
Chuck Rolke commented on DISPATCH-451:
--------------------------------------
The issue is in the units of the AMQP incoming-window and Proton's session
'capacity'.
* AMQP Open max-frame-size and Attach max-message-size are measured in octets.
* AMQP Begin incoming-window is measured in transfers.
* Proton pn_session_set_incoming_capacity is measured in octets.
Proton calculates the negotiated Begin incoming-capacity by dividing the value
of
session incoming capacity by max-frame-size to yield some number of transfers.
Everything is working correctly.
> [AMQP] Hard coded session capacity should be configurable
> ---------------------------------------------------------
>
> Key: DISPATCH-451
> URL: https://issues.apache.org/jira/browse/DISPATCH-451
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 0.6.0
> Reporter: Chuck Rolke
>
> In container.c and policy.c
> {noformat}
> pn_session_set_incoming_capacity(link->pn_sess, 1000000);
> {noformat}
> could be improved.
> Policy provides settable values for Open/maxFrameSize, Open/maxSessions,
> Begin/incoming_window, Attach/maxMessageSize. Configuration settings for
> these are also desirable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
