[
https://issues.apache.org/jira/browse/DISPATCH-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542331#comment-15542331
]
Chuck Rolke commented on DISPATCH-451:
--------------------------------------
After adding code to set the session incoming_capacity (to 987654 instead of
1000000) the exchange between qpid/drain and dispatch is:
{noformat}
Sun Oct 2 08:05:12 2016 SERVER (trace) [2]:0 <- @begin(17)
[next-outgoing-id=0, incoming-window=2147483647, outgoing-window=2147483647]
Sun Oct 2 08:05:12 2016 SERVER (trace) [2]:0 -> @begin(17) [remote-channel=0,
next-outgoing-id=0, incoming-window=8, outgoing-window=2147483647]
{noformat}
incoming-window=8?
# Restoring 1000000 and the value negotiated is still 8.
# Reverting dispatch to master and the value moves to 61.
# Looking closely at traces taken from proton/master, dispatch/master on
20160920 and the value is 61.
I'm working backwards in history to determine if this is a dispatch or a proton
issue.
> [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]
