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
Hi, I am using this sdk in my company where one of our products/services is help customers/users create a consumer and subscribe to topics given by them. There's one case where user provides invalid credentials. We have yet to figure out how to handle this "invalid credentials" case. What is the best way to catch this type of error? Is there a way to catch this upon Initializing PushConsumer? We observe this results in "send heartbeat to broker fails" error during consumption, which seems pretty generic and I believe is not necessarily specific to invalid AkSk.
Any help or guidance is very much appreciated :D
Please describe the issue you observed:
What did you do (The steps to reproduce)?
Create a new Push Consumer with invalid aksk credentials and subscribe to a topic.
What did you expect to see?
Error thrown out about invalid aksk credentials either upon initialization of Push Consumer or during message consumption.
What did you see instead?
log output during consumption:
WARN[0001] send heart beat to broker failed brokerAddr="10.249.160.212:30911" brokerId=0 brokerName=brk-0b82304e-12ad3b0cd86c-6ef1d447009 responseCode=1
Please tell us about your environment:
What is your OS?
macOS Monterey version 12.4
What is your client version?
github.com/apache/rocketmq-client-go/v2 v2.1.0
The text was updated successfully, but these errors were encountered:
The startup of PushConsumer is actually a lazy startup. It would not directly verify the validity of authentication and cannot support your requirements at the moment. The ak/sk is a private permission set by the user, it is recommend that you ensure the correctness of the parameters before use it.
Hi, I am using this sdk in my company where one of our products/services is help customers/users create a consumer and subscribe to topics given by them. There's one case where user provides invalid credentials. We have yet to figure out how to handle this "invalid credentials" case. What is the best way to catch this type of error? Is there a way to catch this upon Initializing PushConsumer? We observe this results in "send heartbeat to broker fails" error during consumption, which seems pretty generic and I believe is not necessarily specific to invalid AkSk.
Any help or guidance is very much appreciated :D
Please describe the issue you observed:
What did you do (The steps to reproduce)?
Create a new Push Consumer with invalid aksk credentials and subscribe to a topic.
What did you expect to see?
Error thrown out about invalid aksk credentials either upon initialization of Push Consumer or during message consumption.
What did you see instead?
log output during consumption:
WARN[0001] send heart beat to broker failed brokerAddr="10.249.160.212:30911" brokerId=0 brokerName=brk-0b82304e-12ad3b0cd86c-6ef1d447009 responseCode=1
Please tell us about your environment:
What is your OS?
macOS Monterey version 12.4
What is your client version?
github.com/apache/rocketmq-client-go/v2 v2.1.0
The text was updated successfully, but these errors were encountered: