[
https://issues.apache.org/jira/browse/DISPATCH-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161413#comment-17161413
]
ASF subversion and git services commented on DISPATCH-1640:
-----------------------------------------------------------
Commit 0cda34980243e4cba32b532cd07204ff0668375a in qpid-dispatch's branch
refs/heads/master from Charles E. Rolke
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=0cda349 ]
DISPATCH-1640: How to avoid having message size limits block edge management
* Interior routers perform max message size checks on message ingress.
Once a message has entered the interior router network it is never again
checked for max message size.
* Edge routers perform max message size checks on message ingress.
Once a message has entered the edge router it may be forwarded to
another locally connected destination and it is not again checked for
max message size.
* Messages that are accepted by an edge router and are then forwarded to
an interior router are also checked for max message size by the interior
router.
* Management requests and responses that are destined to an interior
router are checked for max message size by the interior router.
The recommendation to avoid blocking edge router management is to set
the interior router's max message size greater than the size of expected
edge router management requests and responses. Typically management
responses are larger and are under 5,000,000 bytes.
Another recommendation is to keep edge router max message sizes 1 kilobyte
smaller than the attached interior router max message size. This keeps
edge router connections stable while forwarding edge router user
messages to the interior router network.
This closes #741
> Edge router internal and $management links should be exempt from oversize
> rejection
> -----------------------------------------------------------------------------------
>
> Key: DISPATCH-1640
> URL: https://issues.apache.org/jira/browse/DISPATCH-1640
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Policy Engine, Router Node
> Affects Versions: 1.12.0
> Reporter: Charles E. Rolke
> Assignee: Charles E. Rolke
> Priority: Major
> Fix For: Backlog
>
>
> Oversize messages from an edge router to an interior router will trigger a
> connection close. Management requests and responses, and router protocol
> messages must never trigger a connection close.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
