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
{{ message }}
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
The address controller does not use TLS when checking router for addresses being configured, and prints messages like this:
2017-09-22 08:36:35 INFO AddressController:242 - Error requesting router status. Ignoring
java.util.concurrent.ExecutionException: java.lang.SecurityException: Could not find a suitable SASL mechanism for the remote peer using the available credentials.
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
at io.enmasse.amqp.SyncRequestClient.request(SyncRequestClient.java:94)
at io.enmasse.controller.standard.AddressController.checkRouter(AddressController.java:236)
at io.enmasse.controller.standard.AddressController.checkRouterStatus(AddressController.java:196)
at io.enmasse.controller.standard.AddressController.checkStatuses(AddressController.java:177)
at io.enmasse.controller.standard.AddressController.resourcesUpdated(AddressController.java:113)
at io.enmasse.k8s.api.ResourceController.run(ResourceController.java:72)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.SecurityException: Could not find a suitable SASL mechanism for the remote peer using the available credentials.
at io.vertx.proton.impl.ProtonSaslClientAuthenticatorImpl.handleSaslInit(ProtonSaslClientAuthenticatorImpl.java:140)
at io.vertx.proton.impl.ProtonSaslClientAuthenticatorImpl.process(ProtonSaslClientAuthenticatorImpl.java:89)
at io.vertx.proton.impl.ProtonTransport.processSaslAuthentication(ProtonTransport.java:201)
at io.vertx.proton.impl.ProtonTransport.handleSocketBuffer(ProtonTransport.java:184)
at io.vertx.core.net.impl.NetSocketImpl.handleDataReceived(NetSocketImpl.java:321)
at io.vertx.core.net.impl.NetClientImpl$1.handleMsgReceived(NetClientImpl.java:197)
at io.vertx.core.net.impl.VertxNetHandler.lambda$channelRead$0(VertxNetHandler.java:64)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:335)
at io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:193)
at io.vertx.core.net.impl.VertxNetHandler.channelRead(VertxNetHandler.java:64)
at io.vertx.core.net.impl.VertxHandler.channelRead(VertxHandler.java:122)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:363)
The text was updated successfully, but these errors were encountered:
The address controller does not use TLS when checking router for addresses being configured, and prints messages like this:
2017-09-22 08:36:35 INFO AddressController:242 - Error requesting router status. Ignoring
java.util.concurrent.ExecutionException: java.lang.SecurityException: Could not find a suitable SASL mechanism for the remote peer using the available credentials.
Caused by: java.lang.SecurityException: Could not find a suitable SASL mechanism for the remote peer using the available credentials.
The text was updated successfully, but these errors were encountered: