RockteMQ-AI commented on issue #11358: URL: https://github.com/apache/rocketmq/issues/11358#issuecomment-6117563794
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified against the current codebase (develop branch, commit e1eb99c). **Root Cause:** `ProxyAdminGrpcService` attaches its caller `CompletableFuture` to a `ProxyRelayRequest` and waits on it. Only `ClusterProxyRelayService.bridgeToCaller()` reads that attached future and bridges the relay result into it. In LOCAL mode, `LocalProxyRelayService` never touches the `ProxyRelayRequest`'s attached future — it only synthesizes a remoting response into the co-located broker's `NettyRemotingAbstract.processResponseCommand()` (a path meant for remoting-protocol admin callers). The caller future therefore never completes and the admin RPC always ends at the `withTimeout` deadline. **Impact:** In LOCAL mode (`-pm local`), `GetConsumerRunningInfo`, `PrintThreadStackTrace`, and `VerifyMessage` / `ConsumeMessageDirectly` admin RPCs always timeout after ~6s and return errors, even when the target client is connected and responsive. **Affected files:** - `proxy/.../grpc/admin/ProxyAdminGrpcService.java` - `proxy/.../service/relay/LocalProxyRelayService.java` - `proxy/.../service/relay/ClusterProxyRelayService.java` - `proxy/.../service/relay/ProxyChannel.java` - `proxy/.../service/relay/ProxyRelayRequest.java` **Suggested fix direction:** `LocalProxyRelayService` should bridge the `ProxyRelayRequest`'s attached future the same way `ClusterProxyRelayService` does, while preserving the remoting response-table path for broker-socket callers. An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by RockteMQ-AI* -- 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]
