Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Use TLS for router health check in address controller #242

Closed
lulf opened this issue Sep 22, 2017 · 1 comment
Closed

Use TLS for router health check in address controller #242

lulf opened this issue Sep 22, 2017 · 1 comment
Milestone

Comments

@lulf
Copy link
Member

lulf commented Sep 22, 2017

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)
@lulf
Copy link
Member Author

lulf commented Sep 25, 2017

Fix has been merged

@lulf lulf closed this as completed Sep 25, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant