[
https://issues.apache.org/jira/browse/DISPATCH-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380797#comment-17380797
]
ASF GitHub Bot commented on DISPATCH-2191:
------------------------------------------
asfgit closed pull request #1293:
URL: https://github.com/apache/qpid-dispatch/pull/1293
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Count only body buffers when considering q2. Do not count header buffers
> -------------------------------------------------------------------------
>
> Key: DISPATCH-2191
> URL: https://issues.apache.org/jira/browse/DISPATCH-2191
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 1.16.1
> Reporter: Ganesh Murthy
> Assignee: Ken Giusti
> Priority: Major
>
> Consider a two router case where QD_QLIMIT_Q2_UPPER is set to 32 and
> QD_QLIMIT_Q2_LOWER is set to 16.
> The router B receives a large message from from router A. The first two
> buffers of the message consists of header and properties respectively. This
> is followed by a 16 buffer body data which is followed by a 15 buffer body
> data. There are 33 buffers in total. The application code frees the first
> body data but that frees only 15 buffers because the second body data starts
> in the last buffer of the first body data.
> Out of the original 33 buffers, 15 have been freed which means the number of
> buffers remaining in the message content is 18 which is greater than
> QD_QLIMIT_Q2_LOWER. So we remain in q2 and the second body data is not fully
> received.
>
> This situation can be alleviated by not counting the header buffer towards
> the q2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
