RELEASED: Public: August 7, 2024
Resolved issues
- HA controller should exit if the Hazelcast cluster is broken (BEE-50214)
-
Under some circumstances, such as an OutOfMemoryError caught when processing a message, the Hazelcast system used by an HA controller could shut itself down, but the controller remained running, maybe indefinitely depending on other liveness criteria. Now, when Hazelcast exits unexpectedly for any reason, the controller also exits, to allow a fresh replica to take its place.
- X-Jenkins-Replica-Host & X-Jenkins-Replica-Address headers should follow dev mode (BEE-50665)
-
Previously, the X-Jenkins-Replica-Host & X-Jenkins-Replica-Address headers were added to all HTTP responses in an HA controller. Since these are diagnostic tools, and internal host names or IP addresses can be considered sensitive in some environments, these are now included only when developer mode is enabled, and only for requests authenticated as a user with Overall/SystemRead permission, just like the corresponding notations in the GUI.
-
Internal changes to streamline development. Not user visible. (BEE-50360)
-