[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
|
Hi,
I have tried to run the Hono example, starting the Hono Server and Hono REST Adapter directly via Spring Boot (without Docker). The Dispatch Router runs in the Docker container.
When the REST Adapter tries to connect to Hono, there is this log message in the Hono Server:
---
15:01:16.557 [vert.x-eventloop-thread-7] DEBUG o.e.h.server.HonoSaslAuthenticator - initializing SASL authenticator
15:01:16.596 [vert.x-eventloop-thread-7] DEBUG o.e.h.server.HonoSaslAuthenticator - client provided an empty list of SASL mechanisms [hostname: null, state: PN_SASL_IDLE]
15:01:26.452 [vert.x-eventloop-thread-7] DEBUG o.e.h.server.HonoSaslAuthenticator - client provided an empty list of SASL mechanisms [hostname: null, state: PN_SASL_STEP]
---
This results in this error in the REST Adapter:
---
15:01:26.460 [vert.x-eventloop-thread-0] WARN o.e.h.c.ConnectionFactoryImpl - can't connect to AMQP 1.0 container [localhost:5672]
javax.net.ssl.SSLException: handshake timed out
at io.netty.handler.ssl.SslHandler.handshake(...)(Unknown Source) ~[netty-handler-4.1.5.Final.jar:4.1.5.Final]
---
Can someone give a hint, what I am missing here?
I've taken the environment variables from the respective parts of the docker-compose.yml and added them as parameters to the spring boot run configurations (starting from IDEA), with some adaptations (ports/paths).
--
Best regards
Carsten Lohmann
Bosch Software Innovations GmbH
Schöneberger Ufer 89-91
10785 Berlin
GERMANY
www.bosch-si.com
Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B
Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn