Release: 5.3.2 - #185
Merged
Merged
Release: 5.3.2#185
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 5 line.
Contains #182 (CGroups CPU usage, ported from #180) and #183 (quieter authentication logging, ported from #181).
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 measured against the slice it was allowed while awake, so 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.Cgroupsresolves the process's own cgroup through/proc/self/cgroupand takes the tightest limit up the chain, so a systemd unit withCPUQuota=or a container started with--cgroupns=hostis not mistaken for unlimited.A refused connection is reported once it has persisted, at info rather than error, and only immediately on the first connection an application ever makes. The classifier matches exactly the two phrases the platform produces —
Access Deniedandinvalid authentication— so a TLS or proxy failure mentioning "authentication" is not reported as a credential problem.classifyConnectionErrornow delegates to the same classifier, which matters beyond tidiness: it feedsnotifyUnreachable, andPlatformLicenseSourcemarks a licence unavailable the moment it seesINVALID_AUTHENTICATION. That notification is held back on the same terms as the log line, so a two-second refusal no longer marks a licence unavailable. Other reasons pass through immediately, as they already de-duplicate downstream.The setup payload carries an optional runtime block — JVM, OS, garbage collectors, heap ceiling, and the cgroup's CPU quota, shares and memory limit. The server does not read it yet.
Note on the test suite
AxoniqConsoleRSocketClientToxiproxyIntegrationTesthas four failing tests onmain, unrelated to these changes and present before them — verified by running that class on a clean checkout. Worth a separate look.Follow-up
The development version bump to 5.3.3-SNAPSHOT is in a separate PR and should be merged after this one.