grpc拉取消息时返回空指针异常

[asjfoajs]

grpc拉取时返回CODE: INTERNAL_SERVER_ERROR, MESSAGE: null. NullPointerException. org.apache.rocketmq.proxy.grpc.v2.consumer.ReceiveMessageActivity.receiveMessage(ReceiveMessageActivity.java:66)
查看ReceiveMessageActivity.java:66代码
Settings settings = this.grpcClientSettingsManager.getClientSettings(ctx);
Subscription subscription = settings.getSubscription();
查看getClientSettings方法
public Settings getClientSettings(ProxyContext ctx) {
String clientId = ctx.getClientID();
Settings settings = getRawClientSettings(clientId);
if (settings == null) {
return null;
}
if (settings.hasPublishing()) {
settings = mergeProducerData(settings);
} else if (settings.hasSubscription()) {
settings = mergeSubscriptionData(ctx, settings, settings.getSubscription().getGroup().getName());
}
return mergeMetric(settings);
}
感觉应该是 getClientSettings返回空导致 settings.getSubscription();调用时出现空指针异常，虽然对这段代码加入了try-catch，但是在调用settings.getSubscription();之前，先判断一下settings是否为空，如果为空打印一些日志直接返回，不进行后续操作会比较好一点呢？

[asjfoajs]

小白还想请教一下为啥这个地方会出错呢？看代码应该是获取客户端的信息吧？

[JanYork]

Is this problem solved? I also encountered this problem, can you tell me how you solved it?

[asjfoajs]

I only encountered an error when pulling the message immediately after creating the consumer. I suspect it may be because the consumer has started, but updating the theme subscription relationship is asynchronous and has not yet been completed. Therefore, when pulling the message, it was empty and reported an error. My solution is to delay the consumption for a few seconds after starting it. You can check # 8028, it seems like it hasn't been merged for me yet

[YongXiaoo]

I also encountered this problem, can you tell me how you solved it?

[asjfoajs]

I only encountered an error when pulling the message immediately after creating the consumer. I suspect it may be because the consumer has started, but updating the theme subscription relationship is asynchronous and has not yet been completed. Therefore, when pulling the message, it was empty and reported an error. My solution is to delay the consumption for a few seconds after starting it. You can check # 8028, it seems like it hasn't been merged for me yet