You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this should be classified as an enhancement rather than a bug/feature.
Summary
Returned on the first message pull Failed to receive message for group InitDelContainerGroup: CODE: INTERNAL_SERVER-ERROR, MESSAGE: null NullPointerException Org. apache. locketmq. proxy. grpc. v2. consumer Received Message Activity. receiver Message (Received Message Activity. java: 66)
View code discovery
So when pulling messages without storing client information, I see that storing configuration messages is asynchronously submitted to the client thread pool, which means that the consumer was successfully created, but the configuration information has not been updated yet. When I delay pulling messages after starting the consumer for a period of time, there will be no error.
So I want to return more detailed information to analyze the problem
Motivation
This modification will be more conducive to troubleshooting problems than null pointer exceptions.
Describe the Solution You'd Like
I want to refer to the client's heartbeat method to determine if it is empty and return Code.UNRECOGNIZED_CLIENT_TYPE, "cannot find client settings for this client"
Describe Alternatives You've Considered
I didn't think about it
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Enhancement Request
Summary
Returned on the first message pull
Failed to receive message for group InitDelContainerGroup: CODE: INTERNAL_SERVER-ERROR, MESSAGE: null NullPointerException Org. apache. locketmq. proxy. grpc. v2. consumer Received Message Activity. receiver Message (Received Message Activity. java: 66)
View code discovery
So when pulling messages without storing client information, I see that storing configuration messages is asynchronously submitted to the client thread pool, which means that the consumer was successfully created, but the configuration information has not been updated yet. When I delay pulling messages after starting the consumer for a period of time, there will be no error.
So I want to return more detailed information to analyze the problem
Motivation
This modification will be more conducive to troubleshooting problems than null pointer exceptions.
Describe the Solution You'd Like
I want to refer to the client's heartbeat method to determine if it is empty and return Code.UNRECOGNIZED_CLIENT_TYPE, "cannot find client settings for this client"
Describe Alternatives You've Considered
I didn't think about it
Additional Context
No response
The text was updated successfully, but these errors were encountered: