fengcharly opened a new issue, #6486: URL: https://github.com/apache/rocketmq/issues/6486
Myenv: jdk:1.8 rocketmqversion:5.0.0 prox mode: cluster enableAcl: true What happened: I'm at tool.yml and palin_ Acl.yml is configured with ak/sk, but the proxy sends heartbeat reports to the broker without setting aksk Error message: 2023-03-27 21:12:31 WARN MQClientFactoryScheduledThread - send heart beat to broker[rocketmq-cluster-broker-0 0 10.244.194.140:10911] failed org.apache.rocketmq.client.exception.MQBrokerException: CODE: 1 DESC: org.apache.rocketmq.acl.common.AclException: No accessKey is configured, org.apache.rocketmq.acl.plain.PlainPermissionManager.validate(PlainPermissionManager.java:618) BROKER: 10.244.194.140:10911 For more information, please visit the url, https://rocketmq.apache.org/docs/bestPractice/06FAQ at org.apache.rocketmq.client.impl.MQClientAPIImpl.sendHeartbeat(MQClientAPIImpl.java:1389) at org.apache.rocketmq.client.impl.factory.MQClientInstance.sendHeartbeatToAllBroker(MQClientInstance.java:548) at org.apache.rocketmq.client.impl.factory.MQClientInstance.sendHeartbeatToAllBrokerWithLock(MQClientInstance.java:464) at org.apache.rocketmq.client.impl.factory.MQClientInstance.lambda$startScheduledTask$4(MQClientInstance.java:302) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) -- 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]
