[Bug][SDK] Adjusted frame length exceeds occurred when reporting data through the HTTP protocol

[g0715158]

What happened

When using dataproxy-sdk to report data through the http protocol, the following screenshots report errors:

The scenario description is as follows (SDK only reports one piece of data per startup process):

1. This exception will be reported for the first piece of data reported after the creation of the data stream

2. If the data is not reported for a long time, the first piece of data will report this exception when the data is reported again

Guess the reason for this problem is due to the DataProxy's channel management policy configuration for netty

What you expected to happen

Normal reporting of messages

How to reproduce

repair this bug

Environment

version:1.6.0

InLong version

1.6.0

InLong Component

InLong DataProxy

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dockerzhang]

@gosonzhang PTAL, thanks.

[gosonzhang]

Thanks @g0715158, got it!

[gosonzhang]

Feedback on the current situation of this problem, I plan to optimize the implementation of the Source side [1] first, and use netty to handle HTTP data access. This issue is temporarily reserved, and it will be tested and verified after integration

1. [Improve][DataProxy] Optimize the implementation logic of the Source #7950

[gosonzhang]

Judging from this error message, there are several situations:

1. There is an error in the protocol of the message report, such as TCP reporting to the HTTP port, or the packet format is wrong, resulting in an error in recognition;
2. The format of the message report is correct, but an overlong packet is sent

I found new similar problems in my environment, and I feel that there are still problems, and I need to continue to locate them

[gosonzhang]

This problem should be caused by [1] changes

When the InLong-SDK obtains the access information of the DataProxy reporting node from the Manager, it needs to carry the reporting protocol that the SDK needs to adopt. If the information is not carried, the Manager will return all the reporting ports supported by the DataProxy; in this case, the SDK will Reporting failure occurs because a reporting node with inconsistent protocols is selected.

I will fix this problem, set different reporting protocols according to the created Sender, and store the cached information separately

1. [Improve][SDK] Add protocolType field in DataProxy config #6190