f1amingo opened a new pull request, #1383: URL: https://github.com/apache/rocketmq-clients/pull/1383
### Summary Each Node.js RpcClient now gets its own gRPC subchannel pool, matching the Java client's default connection ownership. Previously, separate client instances targeting the same endpoint with plaintext credentials could share a single TCP connection through grpc-js's global subchannel pool, so a transport-level event such as a server GOAWAY would affect multiple logically independent clients at once. ### Changes - Pass `'grpc.use_local_subchannel_pool': 1` when constructing `MessagingServiceClient` in `nodejs/src/client/RpcClient.ts`. - Add a broker-free regression test verifying independent clients use different connections while telemetry and heartbeat still reuse one connection within a single client. ### How Did You Test This Change? Added `nodejs/test/client/RpcClient.test.ts`, a broker-free test using a local plaintext gRPC server. It fails on master (both clients report the same peer address) and passes after the change. `npm run lint` and `tsc` pass. Relates to #1382 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
