Skip to content

v3.1.2

Release Notes – Version 3.1.2

Contains the changes of hotfix 3.0.9.

Improvements

  • DGNA assignments triggered by rules (e.g. GeoFence DGNA) no longer block the event processing. DGNAs are executed by a dedicated worker: different subscribers are processed in parallel, the DGNAs of one subscriber keep their order.
  • If a newer DGNA for the same subscriber is already waiting, outdated DGNAs (e.g. for GeoFences the subscriber has already left) are skipped and logged to the event log. DGNAs to a group that was assigned successfully shortly before are not sent again.
  • Live positions on the map are processed independently of rules and DGNAs and are no longer delayed by them.
  • Events are processed in parallel per subscriber. Events not processed yet remain in the RabbitMQ queue (GC.Events.Internal) and are processed after a restart of the Internal Event-Processor.
  • RabbitMQ connections for RPC calls and UI notifications are reused instead of being created for every call. RPC calls now have a timeout (default 120 s).
  • The DAMM subscriber no longer waits after the final DGNA result and does not poll when the DGNA could not be sent. The DGNA result is polled every 100 ms (answered locally by the TetraFlex API).
  • The DAMM subscriber respects the TetraFlex limit of 16 simultaneous DGNA instances and retries briefly if no instance is free. DGNA instances are no longer deleted while the DGNA is still pending (only after 60 s as a last resort).
  • Logging: every DGNA is logged with ISSI, target group and the delay since the triggering event. The Internal Event-Processor warns if events are processed more than 30 s after they were created.

Bug Fixes

  • Fixed DGNAs being sent with group address 0 ("Invalid parameter") when the previous group of a subscriber was unknown. These DGNAs are now skipped and logged, and the current group is no longer requested from the subscriber for every DGNA.
  • Fixed Voice Warnings of GeoFences and of rules created before version 3.0.6 failing because of the missing Call Priority / Call Type parameters. Defaults (Pre-emptive priority 4, Simplex group call) are used.
  • Fixed the creation time of events being lost when they are passed to the Internal Event-Processor.

Breaking Changes / Notices

  • Optional settings (appsettings.json), only needed if the defaults do not fit:
  • Internal Event-Processor: Dgna:MaxParallel (default 4, max. 16, max. number of DGNAs sent at the same time; higher values only if the subscribers are spread over many cells), EventProcessing:RuleLanes (default 16), EventProcessing:PositionLanes (default 4), EventProcessing:Prefetch (default 1000)
  • All services: RPC:TimeoutSeconds (default 120)