[Bug] the client can not handle the closed tcp without rst/fin

[absolute8511]

Before Creating the Bug Report

• I found a bug, not just asking a question, which should be created in GitHub Discussions.

• I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

• I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Programming Language of the Client

Java

Runtime Platform Environment

Any

RocketMQ Version of the Client/Server

Any

Run or Compiler Version

Any

Describe the Bug

If the tcp is closed abnormal without a fin or rst, the client will continue send request using the broken channel and will always timeout for a long time. We should turn on the keep alive for the grpc to detect this issue.

Steps to Reproduce

Drop the packets after tcp establish, the client will timeout for a long time.

What Did You Expect to See?

The client should try to create a new connection after keep alive timeout

What Did You See Instead?

the client will timeout for a long time and did not create a new connection

Additional Context

No response

[github-actions]

This issue is stale because it has been open for 30 days with no activity. It will be closed in 3 days if no further activity occurs.

[github-actions]

This issue was closed because it has been inactive for 3 days since being marked as stale.