Carsten Lohmann
Carsten Lohmann
Notable feature: Quarkus 2.11 includes an update to vert.x 4.3, supporting usage of Kafka client 3.0.
When developing the fix for #2660, load-tests have been done with many concurrent device requests for different tenants. The first such request for a tenant causes tenant-specific AMQP links from...
When the MongoDB device registry component is shut down, there may be exceptions like this in the log: ``` WARN org.eclipse.hono.tracing.TracingHelper An unexpected error occurred! java.lang.IllegalStateException: state should be: server...
Compared with previous Hono versions, HTTP requests on the `/liveness` endpoint of Hono components seem to take longer on Hono 2.0 components. This means the Kubernetes liveness probes run into...
When an AMQP/MQTT device, listening for command messages, gets disconnected from the protocol adapter, the association between device id and protocol adapter instance id gets removed in the ~~device connection~~...
This is especially needed for the `KafkaApplicationClient`, letting a given handler be invoked when the Kafka producer is ready. Also introduce a lifecycleStatus in `AbstractServiceClient`, preventing successive start() invocations.
When using Kafka-based messaging: On protocol adapter shutdown, there may be errors like these getting logged: ``` WARN org.eclipse.hono.tracing.TracingHelper An unexpected error occurred! [logged on span [8df2f9a8fbb2799c:33ca4d94d9776346:8ceb03ecb09127ef:1 - forward Event]]...
The given scenario is that of an AMQP or MQTT adapter being shut down while there are a lot of devices still connected and subscribed for commands. The adapter will...
Today there was an integration test run that got stuck. Last log output: ``` 2022-06-28T09:58:49.2283580Z 09:58:49.222 [main] INFO o.e.h.tests.mqtt.TelemetryMqttQoS0IT - running testUploadMessagesViaGateway(VertxTestContext) 2022-06-28T09:58:49.2361887Z 09:58:49.228 [main] INFO o.e.h.tests.IntegrationTestSupport - Configured to...
This issue is about a use case where a device sends a request message and expects a corresponding response from a northbound application. Such a scenario can already be implemented...