Carsten Lohmann
Carsten Lohmann
**Describe the bug** The `io.opentelemetry.opentracingshim.TracerShim#extract(format, carrier)` method is not independent of the current opentelemetry `Context`. If a current opentelemetry `Context` is set, the `TracerShim#extract(format, carrier)` method will return a `SpanContext`...
Request body isn't being logged anymore and inclusion of stacktrace of a client error exception is omitted (usually not needed, e.g. `AbstractHttpEndpoint` already logs it).
Found this exception in CoAP adapter logs: ``` java.lang.NullPointerException at java.base/java.util.Objects.requireNonNull(Unknown Source) at org.eclipse.hono.auth.Device.getPrincipal(Device.java:46) at org.eclipse.hono.auth.Device.(Device.java:40) at org.eclipse.hono.adapter.coap.AbstractHonoResource.lambda$getPutRequestDeviceAndAuth$2(AbstractHonoResource.java:145) at java.base/java.util.Optional.ifPresentOrElse(Unknown Source) at org.eclipse.hono.adapter.coap.AbstractHonoResource.getPutRequestDeviceAndAuth(AbstractHonoResource.java:139) at org.eclipse.hono.adapter.coap.AbstractHonoResource.createCoapContextForPut(AbstractHonoResource.java:195) at org.eclipse.hono.adapter.coap.TracingSupportingHonoResource.handleRequest(TracingSupportingHonoResource.java:182) at org.eclipse.californium.core.server.ServerMessageDeliverer$1.run(ServerMessageDeliverer.java:129) at...
Quote from https://vertx.io/docs/vertx-core/java/#_future_results: > Terminal operations like `onSuccess`, `onFailure` and `onComplete` provide no guarantee whatsoever regarding the invocation order of callbacks. > Consider a future on which 2 callbacks are...
When developing Kafka support in the Command Router, it was made sure that commands get forwarded to the protocol adapter (by publishing on the `command_internal` topic) in the same order...
This fixes #2809.
These Hono 2.0 modules have not been deployed to Maven Central: - hono-client-application - hono-client-application-amqp - hono-client-application-kafka - hono-client-command-amqp - hono-client-device-amqp