The External Event-Processor logs a warning (External EventProcessing channel closed (...), reinitializing) when its RabbitMQ channel is closed and reinitializes itself, including the consumer.
Bug Fixes
Fixed the External Event-Processor silently stopping to consume events while the service kept running. This happened when it published an event before the exchange GC.Events.Internal existed (e.g. External started before the Internal Event-Processor, or after a RabbitMQ restart) or after any other loss of the channel. As a result, no events reached the API: the active subscriber was not set, subscribers were not loaded and the UI showed no data. Only a restart of the service helped.
The External Event-Processor now declares the exchange GC.Events.Internal itself.
Fixed the External Event-Processor continuing without a consumer when starting to consume failed; it now reinitializes.
Fixed a RabbitMQ connection being left open each time the External Event-Processor recreated its channel.
Fixed base stations being shown at a wrong position on the map with the Damm subscriber. The coordinates delivered by the TetraFlex API (milliarcseconds) were converted as microdegrees.
Breaking Changes / Notices
Removed the unused option to start the SubscriberBroker as a child process of the API (Broker section in the API appsettings.json: StartWithApi, Path, MaxRetriesPerHour). The SubscriberBroker has to run as its own Windows Service or container, as in all standard installations.