Proto gRPC Java Stub解析Map类型失败问题排查求助

问题场景 #

开发基于Protobuf的gRPC服务，服务端采用Golang实现，客户端为Java。Proto文件定义了包含Map类型的响应对象，Java客户端发起请求时抛出CANCELLED: Failed to read message.错误。已确认服务端逻辑正常（通过Golang客户端验证），Java请求能到达服务端并收到响应，但Stub无法解析Map类型的响应内容，更换为非Map类型则正常运行。

Proto定义 #

message SomeResponse {
  map<string, Entity> entity_by_id = 1;
}

message Entity {
  uint32 id = 1;
  string name = 2;
}

Java客户端代码片段 #

EntityRequest request = EntityRequest.newBuilder().addExtIds("abc").build();
EntityResponse response;
EntityServiceGrpc.EntityServiceBlockingStub client = EntityServiceGrpc.newBlockingStub(
        ManagedChannelFactory.get(
                InfrastructureProperties.GRPC_HOST,
                InfrastructureProperties.GRPC_PORT
        )
);
try {
    response = client.getEntityByExtIds(request);
} catch (StatusRuntimeException e) {
    // 在此处抛出CANCELLED: Failed to read message.错误
}

版本信息 #

• Golang protoc版本：v4.22.2
• 生成Java Stub的protoc版本：3.23.3
• Java客户端io.grpc版本：1.56.0

核心堆栈信息（已剔除无用行） #

Status{code=CANCELLED, description=Failed to read message., cause=java.lang.NoClassDefFoundError: Could not initialize class com.sixt.service.bbb_bbb_extension.api.GuestOuterClass
    at com.sixt.service.bbb_extension.api.GuestByExtIdsResponse$GuestByExtIdDefaultEntryHolder.<clinit>(GuestByExtIdsResponse.java:56)
    at com.sixt.service.bbb_extension.api.GuestByExtIdsResponse$Builder.mergeFrom(GuestByExtIdsResponse.java:471)
    at com.sixt.service.bbb_extension.api.GuestByExtIdsResponse$1.parsePartialFrom(GuestByExtIdsResponse.java:656)
    at com.sixt.service.bbb_extension.api.GuestByExtIdsResponse$1.parsePartialFrom(GuestByExtIdsResponse.java:648)
    at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:86)
    at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:48)
    at io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller.parseFrom(ProtoLiteUtils.java:242)
    at io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller.parse(ProtoLiteUtils.java:234)
    at io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller.parse(ProtoLiteUtils.java:131)
    at io.grpc.MethodDescriptor.parseResponse(MethodDescriptor.java:284)
    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1MessagesAvailable.runInternal(ClientCallImpl.java:660)
    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1MessagesAvailable.runInContext(ClientCallImpl.java:647)
    at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
    at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
    at io.grpc.stub.ClientCalls$ThreadlessExecutor.runQuietly(ClientCalls.java:777)
    at io.grpc.stub.ClientCalls$ThreadlessExecutor.waitAndDrain(ClientCalls.java:760)
    at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:161)
    at com.sixt.service.ride_user_extension.api.GuestServiceGrpc$GuestServiceBlockingStub.getGuestByExtIds(GuestServiceGrpc.java:397)
Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.NoSuchMethodError: 'boolean com.google.protobuf.DescriptorProtos$FieldDescriptorProto.getProto3Optional()' [in thread "Test worker"]
    at com.google.protobuf.Descriptors$FieldDescriptor.<init>(Descriptors.java:1519)
    at com.google.protobuf.Descriptors$FieldDescriptor.<init>(Descriptors.java:1066)
    at com.google.protobuf.Descriptors$Descriptor.<init>(Descriptors.java:944)
    at com.google.protobuf.Descriptors$Descriptor.<init>(Descriptors.java:657)
    at com.google.protobuf.Descriptors$FileDescriptor.<init>(Descriptors.java:561)
    at com.google.protobuf.Descriptors$FileDescriptor.buildFrom(Descriptors.java:333)
    at com.google.protobuf.Descriptors$FileDescriptor.internalBuildGeneratedFileFrom(Descriptors.java:440)
    at com.google.api.HttpProto.<clinit>(HttpProto.java:57)
    at com.google.api.AnnotationsProto.<clinit>(AnnotationsProto.java:54)
    at com.sixt.service.ride_user_extension.api.GuestOuterClass.<clinit>(GuestOuterClass.java:183)
    at com.sixt.service.ride_user_extension.api.GuestByExtIdsRequest.internalGetFieldAccessorTable(GuestByExtIdsRequest.java:38)
    at com.google.protobuf.GeneratedMessageV3.getDescriptorForType(GeneratedMessageV3.java:139)
    at com.google.protobuf.TextFormat$Printer.print(TextFormat.java:363)
    at com.google.protobuf.TextFormat$Printer.print(TextFormat.java:353)
    at com.google.protobuf.TextFormat$Printer.printToString(TextFormat.java:615)
    at com.google.protobuf.AbstractMessage.toString(AbstractMessage.java:110)
    at net.thucydides.core.steps.StepArgumentWriter.readableFormOf(StepArgumentWriter.java:14)
    at net.thucydides.core.steps.StepNamer.testNameWithArguments(StepNamer.java:42)
    at net.thucydides.core.steps.StepNamer.nameFor(StepNamer.java:19)
    at net.thucydides.core.steps.StepInterceptor.getTestNameFrom(StepInterceptor.java:534)
    at net.thucydides.core.steps.StepInterceptor.notifyStepStarted(StepInterceptor.java:568)
    at net.thucydides.core.steps.StepInterceptor.runOrSkipMethod(StepInterceptor.java:208)
    ... 49 more
}

排查方向 #

• Protobuf依赖版本冲突：堆栈中NoSuchMethodError表明运行时的protobuf版本与生成Stub时依赖的版本不匹配。生成Java Stub使用的protoc 3.23.3对应protobuf-java 3.23.x版本，需检查项目依赖树，排除低版本protobuf依赖，统一使用匹配版本。
• protoc与gRPC版本兼容性：Java客户端io.grpc 1.56.0需与protobuf版本兼容，gRPC 1.56.x推荐搭配protobuf 3.21.x-3.23.x，确认两者版本匹配，避免因不兼容导致解析逻辑异常。
• Stub生成参数问题：检查生成Java Stub的命令是否误使用lite模式（如--grpc-java_opt=lite），lite模式的Stub与标准protobuf解析逻辑存在差异，可能导致Map类型解析失败，确保生成标准Stub。
• 跨版本protoc兼容性：服务端使用protoc 4.22.2，客户端用3.23.3，虽Protobuf跨版本兼容，但需确认是否存在4.x特有的Map序列化逻辑导致3.x客户端无法解析。可尝试将两端protoc版本统一（服务端降级到3.23.x或客户端升级到4.x）后测试。
• 依赖传递问题：检查项目是否通过第三方依赖间接引入了不兼容的protobuf或gRPC版本，通过依赖排除强制统一版本。

内容的提问来源于stack exchange，提问作者Hennadii Bulakh