You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Charles E. Rolke (Jira)" <ji...@apache.org> on 2020/09/28 13:55:00 UTC
[jira] [Commented] (DISPATCH-1778) spurious buffer inserted in body
data
[ https://issues.apache.org/jira/browse/DISPATCH-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203244#comment-17203244 ]
Charles E. Rolke commented on DISPATCH-1778:
--------------------------------------------
TCP Adaptor debug - sending 5 extra bytes (005375A003) from time to time.
Logging in message.c qd_message_body_data_buffers shows the data coming from the message.
* These bytes are not invented by tcp_adaptor.
* [Tnnn] is thread id
* Handle _incoming and _outgoing are executing on two IO threads at the same time.
{code:java}
◊ 2020-09-25 15:31:58.183852 A0#2884 router-a [] [] TCP_ADAPTOR (trace) [C3][L5][T2040248064] handle_incoming ENTRY <<<<<<<<<<<<<<<<<<
◊ 2020-09-25 15:31:58.183949 A0#2885 router-a [] [] TCP_ADAPTOR (trace) [C3][L5] <-- handle_incoming buffer[0] [qd:0x7f9d6c1027d0] has 3 bytes RAW READ: 64 0D 0A
◊ 2020-09-25 15:31:58.184049 A0#2886 router-a [] [] TCP_ADAPTOR (trace) [C2][T2057033472] handle_outgoing ENTRY >>>>>>>>>>>>>>>>>>
◊ 2020-09-25 15:31:58.184170 A0#2887 router-a [] [] TCP_ADAPTOR (trace) [C3][L5] <-- grant read buffer[0] [qd:0x7f9d6c0ebb10]
◊ 2020-09-25 15:31:58.184291 A0#2888 router-a [] [] TCP_ADAPTOR (debug) [C3][L5] Continuing message with 3 bytes
◊ 2020-09-25 15:31:58.184354 A0#2889 router-a [] [] TCP_ADAPTOR (trace) [C3][L5][T2040248064] handle_incoming EXIT <<<<<<<<<<<<<<<<<
◊ 2020-09-25 15:31:58.184391 A0#2890 router-a [] [] TCP_ADAPTOR (debug) [C3] Read 3 bytes
◊ 2020-09-25 15:31:58.184460 A0#2891 router-a [] [] TCP_ADAPTOR (trace) qd_message_body_data_buffers 14 bytes msg-to-raw_buffers 36 38 33 39 63 62 31 33 39 65 39 37 3A 20
◊ 2020-09-25 15:31:58.184546 A0#2892 router-a [] [] TCP_ADAPTOR (trace) qd_message_body_data_buffers 5 bytes msg-to-raw_buffers 00 53 75 A0 03
◊ 2020-09-25 15:31:58.184588 A0#2893 router-a [] [] TCP_ADAPTOR (trace) qd_message_body_data_buffers 3 bytes msg-to-raw_buffers 64 0D 0A
◊ 2020-09-25 15:31:58.184647 A0#2894 router-a [] [] TCP_ADAPTOR (trace) [C2][T2057033472] --> handle_outgoing bufs [qd:(nil)] 14 bytes READ_N_WRITTEN: 36 38 33 39 63 62 31 33 39 65 39 37 3A 20
◊ 2020-09-25 15:31:58.184685 A0#2895 router-a [] [] TCP_ADAPTOR (trace) [C2][T2057033472] --> handle_outgoing bufs [qd:(nil)] 5 bytes READ_N_WRITTEN: 00 53 75 A0 03
◊ 2020-09-25 15:31:58.184718 A0#2896 router-a [] [] TCP_ADAPTOR (trace) [C2][T2057033472] --> handle_outgoing bufs [qd:0x7f9d6c05c0d0] 3 bytes READ_N_WRITTEN: 64 0D 0A
◊ 2020-09-25 15:31:58.184767 A0#2897 router-a [] [] TCP_ADAPTOR (debug) [C2] Writing 22 bytes
◊ 2020-09-25 15:31:58.184800 A0#2898 router-a [] [] TCP_ADAPTOR (trace) [C2][T2057033472] handle_outgoing EXIT >>>>>>>>>>>>>>>>>>
{code}
> spurious buffer inserted in body data
> -------------------------------------
>
> Key: DISPATCH-1778
> URL: https://issues.apache.org/jira/browse/DISPATCH-1778
> Project: Qpid Dispatch
> Issue Type: Sub-task
> Reporter: Gordon Sim
> Priority: Major
>
> When running a simple telnet driven tcp-echo through the tcp adapater in the router I often see a spurious buffer in the body data read on egress from the message. This seems to consist of the data section header, binary code and length.
--
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