GitHub user kongguyoulan3 edited a discussion: 
内网部署了rocketmq5.3.3版本,客户端通过访问公网映射到内网的这个rocketmq,连接失败了,内网可以正常访问

rocketmq version: 5.3.3

broker.conf 配置信息如下:

brokerClusterName = DefaultCluster
brokerName = broker-a
brokerId = 0
deleteWhen = 04
fileReservedTime = 48
brokerRole = ASYNC_MASTER
flushDiskType = ASYNC_FLUSH

storePathRootDir=/opt/rocketmq/store
storePathCommitLog=/opt/rocketmq/store/commitlog
namesrvAddr=0.0.0.0:9876
autoCreateTopicEnable=false

authenticationEnabled = true
authenticationProvider = 
org.apache.rocketmq.auth.authentication.provider.DefaultAuthenticationProvider
initAuthenticationUser = {"username":"rocketmq","password":"12345678"}
innerClientAuthenticationCredentials = 
{"accessKey":"rocketmq","secretKey":"12345678"}
authenticationMetadataProvider = 
org.apache.rocketmq.auth.authentication.provider.LocalAuthenticationMetadataProvider
authorizationEnabled = true
authorizationProvider = 
org.apache.rocketmq.auth.authorization.provider.DefaultAuthorizationProvider
authorizationMetadataProvider = 
org.apache.rocketmq.auth.authorization.provider.LocalAuthorizationMetadataProvider

rmq-proxy.json 配置信息如下:

{
        "rocketMQClusterName": "DefaultCluster",
        "authenticationEnabled": true,
        "remotingListenPort": 8080,
        "grpcServerPort": 8081,
        "authenticationProvider": 
"org.apache.rocketmq.auth.authentication.provider.DefaultAuthenticationProvider",
        "authenticationMetadataProvider": 
"org.apache.rocketmq.proxy.auth.ProxyAuthenticationMetadataProvider",
        "innerClientAuthenticationCredentials": "{\"accessKey\":\"rocketmq\", 
\"secretKey\":\"12345678\"}",
        "authorizationEnabled": true,
        "authorizationProvider": 
"org.apache.rocketmq.auth.authorization.provider.DefaultAuthorizationProvider",
        "authorizationMetadataProvider": 
"org.apache.rocketmq.proxy.auth.ProxyAuthorizationMetadataProvider"
}

客户端连接rocketmq报错信息:
Exception in thread "main" java.lang.IllegalStateException: Expected the 
service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.AbstractService.checkCurrentState(AbstractService.java:384)
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.AbstractService.awaitRunning(AbstractService.java:308)
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.AbstractIdleService.awaitRunning(AbstractIdleService.java:160)
        at 
org.apache.rocketmq.client.java.impl.producer.ProducerBuilderImpl.build(ProducerBuilderImpl.java:93)
        at 
org.example.ProducerSingleton.buildProducer(ProducerSingleton.java:68)
        at org.example.ProducerSingleton.getInstance(ProducerSingleton.java:75)
        at 
org.example.ProducerNormalMessageExample.main(ProducerNormalMessageExample.java:38)
Caused by: java.util.concurrent.CancellationException: Task was cancelled.
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.AbstractFuture.cancellationExceptionWithCause(AbstractFuture.java:1560)
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:590)
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:571)
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.FluentFuture$TrustedFuture.get(FluentFuture.java:91)
        at 
org.apache.rocketmq.client.java.impl.ClientImpl.startUp(ClientImpl.java:188)
        at 
org.apache.rocketmq.client.java.impl.producer.ProducerImpl.startUp(ProducerImpl.java:119)
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.AbstractIdleService$DelegateService.lambda$doStart$0(AbstractIdleService.java:64)
        at 
org.apache.rocketmq.shaded.com.google.common.util.concurrent.Callables.lambda$threadRenaming$3(Callables.java:105)
        at java.lang.Thread.run(Thread.java:750)


GitHub link: https://github.com/apache/rocketmq/discussions/9782

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to