You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/11/03 19:23:00 UTC
[jira] [Commented] (DISPATCH-1806) TCP adaptor mishandles outgoing
body_data
[ https://issues.apache.org/jira/browse/DISPATCH-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225624#comment-17225624 ]
ASF subversion and git services commented on DISPATCH-1806:
-----------------------------------------------------------
Commit 95c3d936f7d6d90fd3760f4cc450f8ca5a4b805a in qpid-dispatch's branch refs/heads/dev-protocol-adaptors-2 from Charles E. Rolke
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=95c3d93 ]
DISPATCH-1806: Account properly for write buffer byte count
Use proper indexes to get written buffer sizes.
> TCP adaptor mishandles outgoing body_data
> -----------------------------------------
>
> Key: DISPATCH-1806
> URL: https://issues.apache.org/jira/browse/DISPATCH-1806
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Protocol Adaptors
> Affects Versions: 1.14.0
> Reporter: Charles E. Rolke
> Assignee: Charles E. Rolke
> Priority: Blocker
> Fix For: 1.15.0
>
>
> * Function read_message_body() calls qd_message_next_body_data() every time it processes up to four body data buffers.
> A vbin segment may contain more than four body data buffers
> * Using a simple (DISPATCH-1778) example a single telnet session may assert that offset is beyond the body_data_buffer_count limit.
> Each vbin segment must track the segment length to know when to stop reading that segment and call qd_message_next_body_data for the next segment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org