Skip to main content

Mango 5.6.x Release Notes

Release notes for all Mango 5.6.x patch releases. The latest release in this series is 5.6.2 (December 15, 2025).

Mango 5.6.2 — December 15, 2025​

core​

  • Jetty upgraded to version 12.1.5. Resolves an issue in Jetty 12.1.x that caused FileMappingHttpContentFactory to serve stale file content even after the files were modified on disk.

ems​

  • Fixed error where the warning icon was not showing according to the value of the point in the device details.
  • Removed cases where date format was hardcoded and not linked to the UI settings configuration.
  • Added restrictions to pages so no page can query items until all of the dropdowns have been populated.
Mango 5.6.1 — December 5, 2025

ui​

  • Users page now has a fixed height in order to avoid the infinite table from loading all items and producing infinite queries.

access-control, cloud-connect, maintenance-events​

  • Resolved an issue where if an active event exists in the database upon Mango startup it was possible for a circular dependency exception to be thrown while loading event type definitions in modules.
Mango 5.6.0 — December 1, 2025

core​

  • Mango is now built and tested using Java 25. Java 25 is fully supported (except if you are using the Chronicle Point Value Cache, in which case Java 21 is the maximum supported version).
  • Java 17 is still the minimum supported version of Java required for Mango to run.
  • The Docker image has been upgraded to use Java 21.
  • Core libraries updated:
    • Spring Framework: 6.2.12
    • Spring Security: 6.5.5
    • Jetty: 12.1.2
    • jOOQ: 3.19.27
    • gRPC: 1.76.0
    • HikariCP: 7.0.2
  • Stability and startup performance improvements: moved the initialization of core services into the Spring context initialization, notably the runtime manager (data sources, data points, and publishers) initialization now happens earlier.
  • Implemented batch writing of event detector state data when terminating data sources or shutting down Mango; this should drastically improve the termination time when using eventPersistence.serviceName=DATABASE.
  • Ensured that data point events are cancelled when disabled data points are deleted.
  • Added JsonData gRPC API for querying, saving, and deleting JSON Store items.
  • Added oauth2.client.registration.{registrationId}.issuerLocation property which allows automatically loading an OAuth2/OIDC configuration from a "well known" URL, simplifying the OAuth2/OIDC authorization code flow login setup. Mango will now exit on startup if the web application context fails to start; use web.exitOnError to configure this behavior.
Breaking Change

Mango no longer maps the built-in "superadmin" role to ROLE_ADMIN. It now uses ROLE_SUPERADMIN instead. Any code or configuration that checks for ROLE_ADMIN granted authority on superadmin users must be updated.

  • Allow purge periods of less than a day — hours and minutes are now selectable.
  • UI cleanup of the "Purge settings" page in "System settings".
  • Event types can now be removed from an event handler when importing via JSON configuration import. Importing with an empty "eventTypes" array will remove all event types from the event handler.
  • Added card style and help information when filtering on event handlers.
  • Fixed an issue causing inconsistencies between the first escalation email and subsequent escalation emails.
  • Enhanced email event handlers to support multiple escalation levels.
  • Added a new Until Inactive escalation mode and configurable limit options to the Email Event Handler.

core, mango-api​

  • Added support for exposing Mango metrics in Prometheus format, useful for monitoring Mango from external tools such as Prometheus.
  • Metrics are available at /rest/latest/system-metrics/prometheus for authenticated superadmin users; access is configurable via a system permission.
  • A separate HTTP server can be enabled on another port to allow anonymous access to metrics at GET /metrics. Set metrics.server.enabled=true to enable; see mango.properties for details.

mango-api​

  • Added new REST API endpoint at /rest/latest/event-types/query-data-point-event-types for finding data point event types by filtering on data point properties.

core, persistent-pub-ds​

  • Fixed a deadlock scenario when terminating publishers, in particular the PTCP publisher.

persistent-pub-ds​

  • The gRPC publisher's republish data feature will now abort republishing if it detects that the persistent queue size has exceeded the "Queue warning size" threshold. Ensure queue sizes are configured appropriately large (at least tens of millions).
  • The gRPC publisher now captures all point values and events even when the publisher is not enabled. Point values and events are continuously recorded into the publisher's persistent queue.
  • A checkbox labeled "Enable offline queuing" in the gRPC publisher editor controls this feature; by default queuing is disabled.
  • Fixed a bug that prevented setting point values back to the publisher/edge from PTCP data source points.
  • Added an option to completely clear the gRPC publisher queue from the UI.

maintenance-events, mango-nosql-database​

  • Implemented fast update of point values in the NoSQL/IasTsdb time series database when retroactively updating point values for past maintenance event periods.

bacnet-ds​

  • BBMD registration is now performed exclusively by the BACnet local device. The data source no longer performs its own BBMD registration on initialization.

mqtt-sparkplug-ds​

  • Tahu library and protobuf definitions upgraded to version 1.0.14.
  • Fixed a bug that occurred when saving birth metrics if the alias value was null.

ui​

  • Fixed an issue where chart annotation shapes were not visible.
  • Removed duplicate import/export button in admin home page/utilities.
  • Added multiple ways to restrict queries from being auto-generated from date bar auto-update events.
  • New UI for managing event types on the event handlers page: a three-pane view with filtering, select-all, and view-selected-only capabilities.
  • Angular services for data point values, events, and statistics are now prevented from running parallel stale requests to the same endpoint.

ems​

  • Added dashboard designer dependency as a restriction to using the EMS module.
  • Fixed issue where migrating from platform manager 5.4.x to a higher version caused new migrated version to show points as disabled.
  • Introduced an EMS setting to allow displaying more than 5 KPIs in Site Overview.
  • Introduced a setting to allow displaying data point values for each device in the device list component in Site Overview.
  • Fixed requests made by the datebar in statistics components.
  • Fixed an issue where from and to from the datebar were not applied to some components in Site Overview.
  • Fixed a bug on Device Type → Metering where the order of the points was not saved correctly.