Re: [hono-dev] Error "client provided an empty list of SASL mechanisms"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
From: "Lohmann Carsten (INST/ECS4)" <Carsten.Lohmann@xxxxxxxxxxxx>
Date: Fri, 27 Jan 2017 13:31:14 +0000
Accept-language: de-DE, en-US
Delivered-to: hono-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/hono-dev>
List-help: <mailto:hono-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/hono-dev>, <mailto:hono-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/hono-dev>, <mailto:hono-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AQHSdyfPxQVKq13ckE2KdmZl33mNnKFKXA0AgAAYfKOAAG07gIAAFT9C///x+gCAAWm4hQ==
Thread-topic: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
We found the issue:
In the list of Hono Server parameters in the IDEA run configuration, "hono.keyStorePath" and "hono.keyStorePassword" were missing.
After adding them, the connection from the REST Adapter to Hono Server works.

--
Mit freundlichen Grüßen / 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


________________________________________
Von: hono-dev-bounces@xxxxxxxxxxx [hono-dev-bounces@xxxxxxxxxxx]&quot; im Auftrag von &quot;Hudalla Kai (INST/ESY1) [Kai.Hudalla@xxxxxxxxxxxx]
Gesendet: Donnerstag, 26. Januar 2017 17:48
An: hono-dev@xxxxxxxxxxx
Betreff: Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection

Can you try to also set the "hono.client.hostnameVerificationRequired=false"
property on the REST adapter?

Also, it might improve readability of the Hono server logs if you'd reduce the
number of instances being deployed to 1 (setting "hono.maxInstances=1")
--
Mit freundlichen Grüßen / Best regards

Kai Hudalla
Chief Software Architect

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

On Thu, 2017-01-26 at 16:41 +0000, Lohmann Carsten (INST/ECS4) wrote:
> Hono Server log:
> ---
> 17:30:58.738 [main] DEBUG o.e.hono.application.Application - Running with
> Spring Boot v1.4.0.RELEASE, Spring v4.3.2.RELEASE
> 17:30:58.739 [main] INFO  o.e.hono.application.Application - The following
> profiles are active: default,dev
> 17:30:58.818 [main] INFO  o.s.c.a.AnnotationConfigApplicationContext -
> Refreshing org.springframework.context.annotation.AnnotationConfigApplicationCo
> ntext@65b3f4a4: startup date [Thu Jan 26 17:30:58 CET 2017]; root of context
> hierarchy
> 17:30:59.736 [main] DEBUG org.eclipse.hono.server.HonoServer - registering
> endpoint [event]
> 17:30:59.737 [main] DEBUG org.eclipse.hono.server.HonoServer - registering
> endpoint [registration]
> 17:30:59.737 [main] DEBUG org.eclipse.hono.server.HonoServer - registering
> endpoint [telemetry]
> 17:30:59.739 [main] INFO  o.e.hono.application.Application - Starting
> authentication service org.eclipse.hono.authentication.impl.AcceptAllPlainAuthe
> nticationService@4275c20c
> 17:30:59.749 [main] INFO  o.e.hono.application.Application - Starting
> authorizaion service org.eclipse.hono.authorization.impl.InMemoryAuthorizationS
> ervice@f27ea3
> 17:30:59.749 [main] INFO  o.e.hono.application.Application - Starting
> registration service FileBasedRegistrationService[filename=device-
> identities.json]
> 17:30:59.753 [vert.x-eventloop-thread-0]
> INFO  o.e.h.a.i.BaseAuthenticationService - listening on event bus [address:
> authentication.in] for incoming authentication messages
> 17:30:59.753 [vert.x-eventloop-thread-1]
> INFO  o.e.h.a.i.BaseAuthorizationService - listening on event bus [address:
> authorization.in] for incoming auth messages
> 17:30:59.753 [vert.x-eventloop-thread-2]
> INFO  o.e.h.r.i.FileBasedRegistrationService - listening on event bus [address:
> registration.in] for incoming registration messages
> 17:30:59.753 [vert.x-eventloop-thread-2] DEBUG
> o.e.h.r.i.FileBasedRegistrationService - trying to load device registration
> information from file device-identities.json
> 17:30:59.754 [vert.x-eventloop-thread-1]
> INFO  o.e.h.a.i.InMemoryAuthorizationService - loading permissions from
> resource file:/home/cal/Projects/hono/config/target/classes/permissions.json
> 17:30:59.808 [vert.x-eventloop-thread-2]
> INFO  o.e.h.r.i.FileBasedRegistrationService - successfully loaded 0 device
> identities from file [device-identities.json]
> 17:30:59.820 [vert.x-eventloop-thread-6]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name:
> registration, class: org.eclipse.hono.registration.impl.RegistrationEndpoint]
> 17:30:59.820 [vert.x-eventloop-thread-6]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: telemetry,
> class: org.eclipse.hono.telemetry.impl.TelemetryEndpoint]
> 17:30:59.823 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [event]
> 17:30:59.823 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [registration]
> 17:30:59.823 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [telemetry]
> 17:30:59.823 [vert.x-eventloop-thread-6]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:30:59.823 [vert.x-eventloop-thread-7]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name:
> registration, class: org.eclipse.hono.registration.impl.RegistrationEndpoint]
> 17:30:59.823 [vert.x-eventloop-thread-7]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: telemetry,
> class: org.eclipse.hono.telemetry.impl.TelemetryEndpoint]
> 17:30:59.824 [vert.x-eventloop-thread-7]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:30:59.824 [vert.x-eventloop-thread-6]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:30:59.824 [vert.x-eventloop-thread-7]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:30:59.826 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [event]
> 17:30:59.826 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [registration]
> 17:30:59.826 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [telemetry]
> 17:30:59.829 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [event]
> 17:30:59.829 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [registration]
> 17:30:59.829 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [telemetry]
> 17:30:59.830 [vert.x-eventloop-thread-9]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name:
> registration, class: org.eclipse.hono.registration.impl.RegistrationEndpoint]
> 17:30:59.830 [vert.x-eventloop-thread-9]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: telemetry,
> class: org.eclipse.hono.telemetry.impl.TelemetryEndpoint]
> 17:30:59.830 [vert.x-eventloop-thread-9]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:30:59.830 [vert.x-eventloop-thread-9]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:30:59.832 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [event]
> 17:30:59.832 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [registration]
> 17:30:59.832 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [telemetry]
> 17:30:59.833 [vert.x-eventloop-thread-10]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name:
> registration, class: org.eclipse.hono.registration.impl.RegistrationEndpoint]
> 17:30:59.834 [vert.x-eventloop-thread-10]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: telemetry,
> class: org.eclipse.hono.telemetry.impl.TelemetryEndpoint]
> 17:30:59.834 [vert.x-eventloop-thread-10]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:30:59.834 [vert.x-eventloop-thread-10]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:30:59.835 [vert.x-eventloop-thread-8]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name:
> registration, class: org.eclipse.hono.registration.impl.RegistrationEndpoint]
> 17:30:59.836 [vert.x-eventloop-thread-8]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: telemetry,
> class: org.eclipse.hono.telemetry.impl.TelemetryEndpoint]
> 17:30:59.836 [vert.x-eventloop-thread-8]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:30:59.836 [vert.x-eventloop-thread-8]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:30:59.837 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [event]
> 17:30:59.837 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [registration]
> 17:30:59.837 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [telemetry]
> 17:30:59.837 [vert.x-eventloop-thread-11]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name:
> registration, class: org.eclipse.hono.registration.impl.RegistrationEndpoint]
> 17:30:59.838 [vert.x-eventloop-thread-11]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: telemetry,
> class: org.eclipse.hono.telemetry.impl.TelemetryEndpoint]
> 17:30:59.838 [vert.x-eventloop-thread-11]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:30:59.838 [vert.x-eventloop-thread-11]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:30:59.840 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [event]
> 17:30:59.840 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [registration]
> 17:30:59.840 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [telemetry]
> 17:30:59.841 [vert.x-eventloop-thread-12]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name:
> registration, class: org.eclipse.hono.registration.impl.RegistrationEndpoint]
> 17:30:59.841 [vert.x-eventloop-thread-12]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: telemetry,
> class: org.eclipse.hono.telemetry.impl.TelemetryEndpoint]
> 17:30:59.841 [vert.x-eventloop-thread-12]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:30:59.841 [vert.x-eventloop-thread-12]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:30:59.843 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [event]
> 17:30:59.843 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [registration]
> 17:30:59.843 [vert.x-eventloop-thread-5] DEBUG
> org.eclipse.hono.server.HonoServer - registering endpoint [telemetry]
> 17:30:59.847 [vert.x-eventloop-thread-13]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name:
> registration, class: org.eclipse.hono.registration.impl.RegistrationEndpoint]
> 17:30:59.847 [vert.x-eventloop-thread-13]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: telemetry,
> class: org.eclipse.hono.telemetry.impl.TelemetryEndpoint]
> 17:30:59.847 [vert.x-eventloop-thread-13]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:30:59.847 [vert.x-eventloop-thread-13]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.327 [vert.x-eventloop-thread-13]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: event,
> class: org.eclipse.hono.event.impl.EventEndpoint]
> 17:31:00.327 [vert.x-eventloop-thread-6]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: event,
> class: org.eclipse.hono.event.impl.EventEndpoint]
> 17:31:00.327 [vert.x-eventloop-thread-12]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: event,
> class: org.eclipse.hono.event.impl.EventEndpoint]
> 17:31:00.327 [vert.x-eventloop-thread-8]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: event,
> class: org.eclipse.hono.event.impl.EventEndpoint]
> 17:31:00.327 [vert.x-eventloop-thread-7]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: event,
> class: org.eclipse.hono.event.impl.EventEndpoint]
> 17:31:00.327 [vert.x-eventloop-thread-13]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:31:00.327 [vert.x-eventloop-thread-10]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: event,
> class: org.eclipse.hono.event.impl.EventEndpoint]
> 17:31:00.327 [vert.x-eventloop-thread-6]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:31:00.327 [vert.x-eventloop-thread-12]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:31:00.327 [vert.x-eventloop-thread-9]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: event,
> class: org.eclipse.hono.event.impl.EventEndpoint]
> 17:31:00.328 [vert.x-eventloop-thread-7]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:31:00.328 [vert.x-eventloop-thread-11]
> INFO  org.eclipse.hono.server.HonoServer - starting endpoint [name: event,
> class: org.eclipse.hono.event.impl.EventEndpoint]
> 17:31:00.328 [vert.x-eventloop-thread-8]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:31:00.328 [vert.x-eventloop-thread-13]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.328 [vert.x-eventloop-thread-10]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:31:00.328 [vert.x-eventloop-thread-6]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.328 [vert.x-eventloop-thread-12]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.328 [vert.x-eventloop-thread-9]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:31:00.328 [vert.x-eventloop-thread-7]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.329 [vert.x-eventloop-thread-8]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.329 [vert.x-eventloop-thread-11]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from file
> [../config/demo-certs/certs/trusted-certs.pem] as trust anchor
> 17:31:00.329 [vert.x-eventloop-thread-10]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.333 [vert.x-eventloop-thread-9]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.335 [vert.x-eventloop-thread-11]
> INFO  o.e.h.c.HonoClientConfigProperties - using key & certificate from PKCS12
> key store [../config/demo-certs/certs/honoKeyStore.p12] for identity
> 17:31:00.382 [vert.x-eventloop-thread-9]
> INFO  org.eclipse.hono.server.HonoServer - HonoServer running at
> [127.0.0.1:5672]
> 17:31:00.382 [vert.x-eventloop-thread-12]
> INFO  org.eclipse.hono.server.HonoServer - HonoServer running at
> [127.0.0.1:5672]
> 17:31:00.382 [vert.x-eventloop-thread-13]
> INFO  org.eclipse.hono.server.HonoServer - HonoServer running at
> [127.0.0.1:5672]
> 17:31:00.382 [vert.x-eventloop-thread-7]
> INFO  org.eclipse.hono.server.HonoServer - HonoServer running at
> [127.0.0.1:5672]
> 17:31:00.382 [vert.x-eventloop-thread-6]
> INFO  org.eclipse.hono.server.HonoServer - HonoServer running at
> [127.0.0.1:5672]
> 17:31:00.382 [vert.x-eventloop-thread-8]
> INFO  org.eclipse.hono.server.HonoServer - HonoServer running at
> [127.0.0.1:5672]
> 17:31:00.382 [vert.x-eventloop-thread-11]
> INFO  org.eclipse.hono.server.HonoServer - HonoServer running at
> [127.0.0.1:5672]
> 17:31:00.382 [vert.x-eventloop-thread-10]
> INFO  org.eclipse.hono.server.HonoServer - HonoServer running at
> [127.0.0.1:5672]
> 17:31:00.383 [main] INFO  o.e.hono.application.Application - Hono startup
> completed successfully
> 17:31:00.523 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter - Registering beans
> for JMX exposure on startup
> 17:31:00.535 [main] INFO  o.e.hono.application.Application - Started
> Application in 2.475 seconds (JVM running for 2.88)
>
> 17:31:46.388 [vert.x-eventloop-thread-13] DEBUG
> o.e.h.server.HonoSaslAuthenticator - initializing SASL authenticator
> 17:31:46.424 [vert.x-eventloop-thread-13] DEBUG
> o.e.h.server.HonoSaslAuthenticator - client provided an empty list of SASL
> mechanisms [hostname: null, state: PN_SASL_IDLE]
> 17:31:56.321 [vert.x-eventloop-thread-13] DEBUG
> o.e.h.server.HonoSaslAuthenticator - client provided an empty list of SASL
> mechanisms [hostname: null, state: PN_SASL_STEP]
> ---
>
>
> REST Adapter logs:
> ---
> 17:31:44.632 [main] DEBUG o.e.hono.adapter.rest.Application - Running with
> Spring Boot v1.4.0.RELEASE, Spring v4.3.2.RELEASE
> 17:31:44.632 [main] INFO  o.e.hono.adapter.rest.Application - The following
> profiles are active: dev
> 17:31:44.705 [main] INFO  o.s.c.a.AnnotationConfigApplicationContext -
> Refreshing org.springframework.context.annotation.AnnotationConfigApplicationCo
> ntext@6ae5aa72: startup date [Thu Jan 26 17:31:44 CET 2017]; root of context
> hierarchy
> 17:31:45.731 [main] DEBUG
> o.e.h.a.r.Application$$EnhancerBySpringCGLIB$$996eca8d - starting up 1
> instances of 'REST' adapter verticle
> 17:31:46.217 [vert.x-eventloop-thread-0]
> INFO  o.e.h.c.HonoClientConfigProperties - using certificates from JKS key
> store [../../config/demo-certs/certs/trustStore.jks] as trust anchor
> 17:31:46.318 [vert.x-eventloop-thread-0]
> INFO  o.e.h.a.r.VertxBasedRestProtocolAdapter - Hono REST adapter running on
> 0.0.0.0:8080
> 17:31:46.319 [vert.x-eventloop-thread-1] DEBUG
> o.e.h.a.r.Application$$EnhancerBySpringCGLIB$$996eca8d - verticle instance 1
> deployed
> 17:31:46.319 [main]
> INFO  o.e.h.a.r.Application$$EnhancerBySpringCGLIB$$996eca8d - 'REST' adapter
> startup completed successfully
> 17:31:46.484 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter - Registering beans
> for JMX exposure on startup
> 17:31:46.497 [main] INFO  o.e.hono.adapter.rest.Application - Started
> Application in 2.4 seconds (JVM running for 2.818)
> 17:31:56.326 [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]
> ---
>
>
> --
>
> Mit freundlichen Grüßen / 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
>
>
>
> ________________________________________
> Von: hono-dev-bounces@xxxxxxxxxxx [hono-dev-bounces@xxxxxxxxxxx]&quot; im
> Auftrag von &quot;Hudalla Kai (INST/ESY1) [Kai.Hudalla@xxxxxxxxxxxx]
> Gesendet: Donnerstag, 26. Januar 2017 17:22
> An: hono-dev@xxxxxxxxxxx
> Betreff: Re: [hono-dev] Error "client provided an empty list of SASL
> mechanisms" on Protocol Adapter to Hono connection
>
> Looks ok so far.
>
> Can you enable DEBUG logging in the Hono server and post the output of the
> server
> log so that we can better see what's happening?
> --
> Mit freundlichen Grüßen / Best regards
>
> Kai Hudalla
> Chief Software Architect
>
> 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
>
> On Thu, 2017-01-26 at 16:15 +0000, Lohmann Carsten (INST/ECS4) wrote:
> > the Run configuration for the *Hono server* contains these
> > options/parameters:
> > [...]
> >     <option name="SPRING_BOOT_MAIN_CLASS"
> > value="org.eclipse.hono.application.Application" />
> >     <option name="ACTIVE_PROFILES" value="default,dev" />
> >     <option name="WORKING_DIRECTORY" value="file://$MODULE_DIR$" />
> >     <option name="ALTERNATIVE_JRE_PATH" />
> >     <additionalParameters>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.downstream.host" />
> >         <option name="value" value="localhost" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.downstream.port" />
> >         <option name="value" value="15673" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.downstream.keyStorePath" />
> >         <option name="value" value="../config/demo-
> > certs/certs/honoKeyStore.p12" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.downstream.keyStorePassword" />
> >         <option name="value" value="honokeys" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.downstream.trustStorePath" />
> >         <option name="value" value="../config/demo-certs/certs/trusted-
> > certs.pem" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name"
> > value="hono.downstream.hostnameVerificationRequired" />
> >         <option name="value" value="false" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="logging.config" />
> >         <option name="value" value="classpath:logback-spring.xml" />
> >       </param>
> >     </additionalParameters>
> > [...]
> >
> >
> >
> > The *REST adapter*:
> > [...]
> >     <option name="SPRING_BOOT_MAIN_CLASS"
> > value="org.eclipse.hono.adapter.rest.Application" />
> >     <option name="ACTIVE_PROFILES" value="dev" />
> >     <option name="WORKING_DIRECTORY" value="file://$MODULE_DIR$" />
> >     <option name="ALTERNATIVE_JRE_PATH" />
> >     <additionalParameters>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.client.name" />
> >         <option name="value" value="Hono REST Adapter" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.client.host" />
> >         <option name="value" value="localhost" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.client.port" />
> >         <option name="value" value="5672" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.client.username" />
> >         <option name="value" value="rest-adapter" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.client.password" />
> >         <option name="value" value="secret" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.client.trustStorePath" />
> >         <option name="value" value="../../config/demo-
> > certs/certs/trustStore.jks" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.client.trustStorePassword" />
> >         <option name="value" value="honotrust" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.http.bindaddress" />
> >         <option name="value" value="0.0.0.0" />
> >       </param>
> >       <param>
> >         <option name="enabled" value="true" />
> >         <option name="name" value="hono.maxInstances" />
> >         <option name="value" value="1" />
> >       </param>
> >     </additionalParameters>
> > [...]
> >
> > The paths in the variable values have been adapted from the ones in the
> > docker-
> > compose.yml file (reading the corresponding files looks ok to me).
> > The values "hono.downstream.host" and "hono.downstream.port" of Hono Server
> > have been adapted to localhost:15673.
> >
> > --
> >  Mit freundlichen Grüßen / 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
> >
> >
> >
> >
> >
> > ________________________________________
> > Von: hono-dev-bounces@xxxxxxxxxxx [hono-dev-bounces@xxxxxxxxxxx]&quot; im
> > Auftrag von &quot;Hudalla Kai (INST/ESY1) [Kai.Hudalla@xxxxxxxxxxxx]
> > Gesendet: Donnerstag, 26. Januar 2017 09:24
> > An: hono-dev@xxxxxxxxxxx
> > Betreff: Re: [hono-dev] Error "client provided an empty list of SASL
> > mechanisms" on Protocol Adapter to Hono connection
> >
> > Hi Carste,
> >
> > can you provide a list of the environment variables or command line options
> > you
> > use for starting the Hono server and REST adapter from within IntelliJ?
> >
> > I suspect this to be a case of a missing/wrong option/variable...
> > --
> > Mit freundlichen Grüßen / Best regards
> >
> > Kai Hudalla
> > Chief Software Architect
> >
> > 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
> >
> > On Wed, 2017-01-25 at 16:29 +0000, Lohmann Carsten (INST/ECS4) wrote:
> > > 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
> > > _______________________________________________
> > > hono-dev mailing list
> > > hono-dev@xxxxxxxxxxx
> > > To change your delivery options, retrieve your password, or unsubscribe
> > > from
> > > this list, visit
> > > https://dev.eclipse.org/mailman/listinfo/hono-dev
> >
> > _______________________________________________
> > hono-dev mailing list
> > hono-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from
> > this list, visit
> > https://dev.eclipse.org/mailman/listinfo/hono-dev
> > _______________________________________________
> > hono-dev mailing list
> > hono-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from
> > this list, visit
> > https://dev.eclipse.org/mailman/listinfo/hono-dev
>
> _______________________________________________
> hono-dev mailing list
> hono-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/hono-dev
> _______________________________________________
> hono-dev mailing list
> hono-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/hono-dev
_______________________________________________
hono-dev mailing list
hono-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/hono-dev
Follow-Ups:
- Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
  - From: Hudalla Kai (INST/ESY1)
References:
- [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
  - From: Lohmann Carsten (INST/ECS4)
- Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
  - From: Hudalla Kai (INST/ESY1)
- Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
  - From: Lohmann Carsten (INST/ECS4)
- Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
  - From: Hudalla Kai (INST/ESY1)
- Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
  - From: Lohmann Carsten (INST/ECS4)
- Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
  - From: Hudalla Kai (INST/ESY1)
Prev by Date: Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
Next by Date: Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
Previous by thread: Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
Next by thread: Re: [hono-dev] Error "client provided an empty list of SASL mechanisms" on Protocol Adapter to Hono connection
Index(es):
- Date
- Thread
Breadcrumbs
