[ 
https://issues.apache.org/jira/browse/DISPATCH-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219481#comment-17219481
 ] 

ASF subversion and git services commented on DISPATCH-1751:
-----------------------------------------------------------

Commit 7525ac665c3600805615c86796482914cdba783d in qpid-dispatch's branch 
refs/heads/dependabot/npm_and_yarn/console/react/d3-6.2.0 from Charles E. Rolke
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=7525ac6 ]

DISPATCH-1751: Rework how AMQP session incoming-window is derived

Proton allows specification of a session 'capacity'. Initially the
incoming-window will be (capacity / max-frame-size), defining at most
how many max-size transfers will definitely be accepted on the session.

Dispatch listener config defines a maxFrameSize and a maxSessionFrames
the product of which is equal to the capacity to be configured in Proton.

Dispatch vhostUserGroup policy defines a maxFrameSize and a
maxSessionWindow. The maxSessionWindow is passed directly to Proton
as the capacity.

This closes #847


> unexpected incoming-window in begin frame when running Dispatch on 32 bit 
> system
> --------------------------------------------------------------------------------
>
>                 Key: DISPATCH-1751
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1751
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 1.13.0
>            Reporter: Ganesh Murthy
>            Priority: Major
>             Fix For: 1.15.0
>
>
> On 32bit systems, an unexpected incoming-window value is set. This for 
> example causes system_tests_protocol_settings failures on 32bit systems, with 
> test expecting to see the incoming-window be 2147483647 but instead finding 
> it much less, e.g 131071.
> This is due to the way the session capacity is configured, particularly on 
> 32bit systems. See more details (output, code, etc) from prior discussions on 
> PROTON-2255 (raised when this was incorrectly thought to be a proton issue).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to