Minor Releases

This page aims to provide a dedicated overview of patch releases for the Axon Server releases

Axon Server Standard Edition

Release 4.4

Release 4.4.4

Improved QueryService logging
Added preserve event store option to delete context CLI command
Fixed stream completed by the server in case of inactivity
Hide upload license panel in SE
Reduced number of open index files
Fix for GetTokenAt operation

Release 4.4.3

Fix for connections not correctly registered
Changed initialization sequence for event store to initialize completed segments first

Release 4.4.2

Offload expensive data-writing operations to a separate thread pool
Fix for reading aggregates with older snapshots

Release 4.4.1

Reduced latency when Tracking live Events from a follower
Improved handling of full queue to client
Fix the refresh of the event processor status

Release 4.3

Release 4.3.6

Fixed concurrency issue in subscribing/unsubscribing commands

Release 4.3.5

Fixed logging in IndexManager

Release 4.3.4

Reduced risk for contention when opening an index file
Offload expensive data-fetching operations to separate thread pool
Option to configure the way that index files are opened (memory mapped or file channel based)
Limit the amount of commands/queries held in Axon Server waiting for the handlers to be ready to handle them, to avoid
out of memory errors on Axon Server

Release 4.3.3

Fix for validation error starting up when there are multiple snapshot files (Standard Edition only)

Release 4.3.2

Fix for tracking event processor updates to websocket causing high CPU load in specific situation
Reduced warnings in log file on clients disconnecting
Fix for concurrency issue in sending heartbeat while client connects/disconnects

Release 4.3.1

Updated usage output in CLI
Updated gRPC/Netty versions
Prevent errors in log (sending ad-hoc result to client that has gone, sending heartbeat to client that has gone)

Release 4.2

Release 4.2.4

Improved support for running management server on separate port

Release 4.2.3

Fix for pending queries with lost connection

Release 4.2.2

Added instruction acknowledgements
Client applications heartbeat support
Cleaned-up logging
Fix for specific error while reading aggregate
Optional heartbeat between Axon Server and Axon Framework clients

Release 4.2.1

Fixes required for enterprise edition only

Release 4.1

Release 4.1.7

Use info endpoint to retrieve version number and product name
Reset reserved sequence numbers for aggregate when storing the event failed

Release 4.1.6

Added operation to set cached version numbers for aggregates

Release 4.1.5

Fix for authorization path mapping and improvements for rest access control
Improvements in release procedure for docker images
Fix for subscription query memory leak
Improvements in error reporting in case of disconnected applications
Improvements in detection of insufficient disk space

Release 4.1.4

Fix for appendEvent with no events in stream

Release 4.1.3

CLI commands now can be performed locally without token.

Release 4.1.2

Status displayed for tracking event processors fixed when segments are running in different applications
Tracking event processors are updated in separate thread
Logging does not show application data anymore
Changed some gRPC error codes returned to avoid clients to disconnect when no command handler found for a command

Release 4.1.1

Sources now available in public GitHub repository
Merge tracking event processor not always available when it should
Logging changes
GRPC version update

Axon Server Enterprise Edition

Release 4.4

Release Notes for version 4.4.6

Improved QueryService logging
Added preserve event store option to delete context CLI command
Fixed stream completed by the server in case of inactivity
Hide upload license panel in SE
Reduced number of open index files
Fix for GetTokenAt operation
Improved feedback on license upload errors
Fix timing issue in leader change potentially causing duplicate events
New REST endpoint to download a diagnostics zip file

Release Notes for version 4.4.5

Fix for connections not correctly registered
Changed initialization sequence for event store to initialize completed segments first
Changed order of files in the backup endpoint for contexts with a jump skip index to list the global index files
before the segment index files
Fix timing issue when a follower sends new events to a new leader before it is fully initialized
Improved logging and error handling for log compaction task

Release Notes for version 4.4.4

Fix for initializing jump skip index when it has more than 1 segment
Improved error handling for problems creating a context and storing events/snapshots
Offload expensive data-writing operations to separate thread pool
Fix for reading aggregates with older snapshots

Release Notes for version 4.4.3

Fix race condition in queries and commands handlers unsubscription during reconnection
Fix pre-vote election with active backup nodes
Axon Server SE improvements from 4.4 to 4.4.1
Fixed issue causing added latency while Tracking live Events from a follower node
Fix the event processor status refresh process

Release Notes for version 4.4.2

Fix for downloading and starting with cluster templates
Renamed field replicationsGroups to replicationGroup in cluster template
Fix storing entries when a context is created with pre-existing event store
Fix query from dashboard when query is executed from admin node and the target context is not defined on this admin node
Fix for timing issue in sharing metrics between Axon Server nodes causing exception during delete context

Release 4.4.1

Fix for migration of contexts created before version 4.3

Release 4.3

Release 4.3.7

Fixed concurrency issue in subscribing/unsubscribing commands

Release 4.3.6

Do not override log entries in RAFT log that already have been committed

Release 4.3.5

Fix for scheduling of tasks in clustering module
Do not override log entries in RAFT log that already have been committed
Fixed logging in IndexManager

Release 4.3.4

Reduced risk for contention when opening an index file
Offload expensive data-fetching operations to separate thread pool
Option to configure the way that index files are opened (memory mapped or file channel based)
Limit the amount of commands/queries held in Axon Server waiting for the handlers to be ready to handle them, to avoid
out of memory errors on Axon Server
Fix for high number of cluster-request threads being created
Fix for timing issue in delete context. This could leave the context existing on one of the member nodes
Fix RAFT bug: configuration changes are not allowed before an entry has been committed in the current term.

New configuration properties added for Axon Server:

axoniq.axonserver.data-fetcher-threads=24 (number of threads that are allocated for doing longer running operations on the event store)

axoniq.axonserver.command-queue-capacity-per-client=10000 (number of command requests for a specific command handling client that Axon Server will cache waiting for permits)

axoniq.axonserver.query-queue-capacity-per-client=10000 (number of query requests for a specific query handling client that Axon Server will cache waiting for permits)

axoniq.axonserver.replication.use-mmap-index=null (by default, AxonServer will determine whether to use memory mapped indexes for replication logs based on operating system and java version, in rare cases it may be useful to override the default)

axoniq.axonserver.replication.force-clean-mmap-index=null (option to forcefully close unused memory mapped files instead of leaving the garbage collector do this, by default, AxonServer will determine this based on operating system and java version, in rare cases it may be useful to override the default)

axoniq.axonserver.event.use-mmap-index=null (by default, AxonServer will determine whether to use memory mapped indexes for event files in the event store based on operating system and java version, in rare cases it may be useful to override the default)

axoniq.axonserver.event.force-clean-mmap-index=null (option to forcefully close unused memory mapped files instead of leaving the garbage collector do this, by default, AxonServer will determine this based on operating system and java version, in rare cases it may be useful to override the default)

axoniq.axonserver.snapshot.use-mmap-index=null (by default, AxonServer will determine whether to use memory mapped indexes for snapshot files in the event store based on operating system and java version, in rare cases it may be useful to override the default)

axoniq.axonserver.snapshot.force-clean-mmap-index=null (option to forcefully close unused memory mapped files instead of leaving the garbage collector do this, by default, AxonServer will determine this based on operating system and java version, in rare cases it may be useful to override the default)

Configuration properties default values changed:

axoniq.axonserver.cluster-executor-thread-count=4 (reduced from 8, configures the number of threads used to handle requests from other axon server nodes, reduced as effective processing of the requests if offloaded to other threads)

axoniq.axonserver.executor-thread-count=4 (reduced from 8, configures the number of threads used to handle requests from clients, reduced as effective processing of the requests if offloaded to other threads)

Release 4.3.3

Fix for race condition during rollback of transaction log

Release 4.3.2

Fix for tracking event processor updates to websocket causing high CPU load in specific situation
Reduced warnings in log file on clients disconnecting
Fix for concurrency issue in sending heartbeat while client connects/disconnects

Release 4.3.1

Updated usage output in CLI
Updated gRPC/Netty versions
Prevent errors in log (sending ad-hoc result to client that has gone, sending heartbeat to client that has gone)
Fix in CLI, application list failed
Removed retry option from H2 controldb URL
Fixed Axon Server keeping incorrect application references on restart of Axon Server node where application was connected
Fixed race condition when two Axon Server nodes are trying to become member of the same context at the same time
Fix for some REST reads were able with invalid token
Clean up of server shutdown process
Fixed error when adding a non-existing node to a context

Release 4.2

Release 4.2.6

Rollback in log entry could cause cluster member to transition to fatal state when there were writes pending

Release 4.2.5

Fix for start-up issue when management.server.port is set