Release: 1.10.5 - #184
Merged
Merged
Release: 1.10.5#184
Conversation
|
stefanmirkovic
approved these changes
Sep 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases the Axon Framework 4 line.
Contains #180 (CGroups CPU usage) and #181 (quieter authentication logging).
What is in it
CPU usage is measured against elapsed time.
getProcessCpuLoad/getCpuLoadare container-aware since JDK 14: under a cgroup quota the JDK divides CPU used byquota * nr_periods, andnr_periodscounts only the scheduling periods in which the cgroup had a runnable task. An idle application was therefore measured against the slice it was allowed while awake — its reading rose as it got quieter and saturated at the 1.0 the JDK clamps to. Both readings now come from monotonic counters over wall time: process CPU time, and/proc/stat.Verified on our own production, before and after, as total CPU over 90 minutes:
Nothing reads above truth any more. The busy applications were already accurate and stayed so.
A refused connection is reported once it has persisted. The client announced an authentication failure on the first refusal, at ERROR, and repeated it every attempt. A 2.3-second gateway gap during a node rotation therefore told customers to check credentials that were fine. It now reports a refusal immediately only on the first connection an application ever makes, and periodically thereafter, at info.
The setup payload carries an optional runtime block — JVM, OS, garbage collectors, heap ceiling, and the cgroup's CPU quota, shares and memory limit. Without it a CPU percentage has no denominator. The server does not read it yet.
Follow-up
The development version bump to 1.10.6-SNAPSHOT is in a separate PR and should be merged after this one.