[Bug] The SDKs of different languages exhibit different unexpected scenarios After restarting the proxy on port 8081 of RocketMQ version 5.3.1

[jiaminzou888]

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.

Runtime platform environment

OS: rocketmq is running in Centos 7.9, clients are running in MacOS, Windows or Linux

RocketMQ version

1. mq version:
   release 5.3.1

2. sdk version:
   cpp: github, rocketmq-clients/cpp, latest source code
   golang: github, rocketmq-clients/golang, v5.1.1-rc1
   java: maven, org.apache.rocketmq, rocketmq-client-java, 5.0.7

JDK Version

openjdk 1.8

Describe the Bug

When I restart the proxy service of RocketMQ, different unexpected errors will occur in the clients of SDKs in different languages:

1. The client in Java language has no error, but it can no longer receive the latest messages under the specified topic. It must restart my server to receive normally.
   "
   cannot receive any messages before i restart my java sdk client
   "

2. The client program in Go language+ report an error.
   "
   rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type "text/plain; charset=utf-8"
   ".

3. The client program in C++ language will core dump.
   "
   [ROCKETMQ-8] Standardize build script. #5 0x000000000057b10d in grpc::ClientBidiReactor<apache::rocketmq::v2::TelemetryCommand, apache::rocketmq::v2::TelemetryCommand>::AddMultipleHolds (this=0x12265d60, holds=1) at /usr/include/grpcpp/support/client_callback.h:309
   [ROCKETMQ-5] Avoid creating directories in UtilAll#getDiskPartitionSp… #6 0x0000000000579d3b in grpc::ClientBidiReactor<apache::rocketmq::v2::TelemetryCommand, apache::rocketmq::v2::TelemetryCommand>::AddHold (this=0x12265d60) at /usr/include/grpcpp/support/client_callback.h:306
   [ROCKETMQ-3] Clean up and perfect the unit test of rocketmq-broker #7 0x0000000000576dc9 in rocketmq::TelemetryBidiReactor::tryWriteNext (this=0x12265d60)
   "

Steps to Reproduce

1. restart the proxy which listened on 8081
2. obeserve the client's log

What Did You Expect to See?

reconnect to the proxy and receive the latest messages then

What Did You See Instead?

things happened as i described in bug detail

Additional Context

No response

[lizhimins]

Some issues with the C++ Client were fixed last week, so you can try it again

@guyinyou， could you please take a look at the Go error?

[jiaminzou888]

Some issues with the C++ Client were fixed last week, so you can try it again

@guyinyou， could you please take a look at the Go error?

Thank You! I'll try it again with C++ Client.

Could You help me to @ some developers who worked on Java SDK ?

[DeerplayHub]

I am using the 5.3.3 version of the Java client. After restarting the proxy, the consumers were able to continue their consumption. Therefore.

Please upgrade the Java client and try again.