axoniq/axonserver repository overview

⁠Axon Server

⁠Supported tags

• Eclipse Temurin based, multi-platform images:

  Axon Server is installed in "/axonserver" and the exported volumes are "/axonserver/data" (ControlDB and PID file), "/axonserver/events" (events and snapshots), "/axonserver/log" (replication log), "/axonserver/config" (for an optional extra "axonserver.properties" file), and "/axonserver/plugins" (for the plugin cache).

  • 2026.0.3, 2026.0.3-jdk-21, latest, latest-jdk-21

    These run Axon Server as user "root" using a Java 21 runtime.

  • 2026.0.3-nonroot, 2026.0.3-jdk-21-nonroot, latest-nonroot, latest-jdk-21-nonroot

    These run Axon Server as user "axonserver" using a Java 21 runtime.

Previous versions can be found in the tags section.

⁠Quick Reference

⁠License Summary:

Axon Server is licensed under the Axoniq Software Subscription Agreement Terms (https://lp.axoniq.io/axoniq-software-subscription-agreement-terms⁠)

You may not use this software except in compliance with these terms.

Permitted use of the software: only for non-production use and deployment not exceeding 14 days. See the license terms for the specific language governing permissions and limitations. No support is provided and the software comes "AS IS" without warranty.

⚠️ IMPORTANT: Production use and/or continued deployment after 14 days requires a commercial license. Go to https://www.axoniq.io⁠ for details.

⁠Where to get information:

• The Axon Reference Guide⁠ is the definitive guide on the Axon Framework and Axon Server.
• Release notes⁠ for all versions
• Visit www.axoniq.io⁠ to find out about AxonIQ, the team behind the Axon Framework and Server.
• Subscribe to the AxonIQ Youtube channel⁠ to get the latest Webinars, announcements, and customer stories.
• The latest version of the Giftcard App can be found on GitHub⁠.
• Docker images for Axon Server are pushed to Docker Hub⁠.

⁠Maintained by:

The AxonIQ team⁠

⁠Release Notes for version 2025.2.0

New Features:

• Analytics nodes to support SQL and natural language queries on event data:
  • Dedicated node(s) for running analytics workloads
  • Improved performance and scalability for analytics tasks
  • Insights agent for LLM integrations
  • MCP support for analytics nodes
• Full support for Dynamic Consistency Boundaries (DCB) including event re-tagging capabilities:
  • Add new tags to existing events without modification of event data
  • Remove existing tags from events as needed
• Snapshot support for DCB contexts
• Backup/restore support for DCB contexts
• UI improvements:
  • List view for the topology overview page

Note: DCB contexts created with the beta feature in 2025.1.0 will require you to remove a file rainbow.lsi prior to upgrading, as it's defaults have changed. This only affects DCB contexts.

⁠Release Notes for version 2025.1.0

Axon Server 2025.1 introduces support for Dynamic Consistency Boundaries (DCB). For more information, see https://docs.axoniq.io/axon-server-reference/v2025.1/rn-as-major-releases/⁠. DCB requires Axon Framework 5.0 or higher.

Bug fixes and improvements:

• Replace CLOB/BLOB fields in configuration DB with varchar/varbinary fields to avoid database size increase
• Fix timing issue with closing indexes on event transformation
• Prevent too many requests from UI to Axon Server
• Fix concurrency issue in reading the term of a replication item while the latest segment is being closed
• Upgrade Spring-Boot to 3.3.13 to address CVE-2025-48988

⁠Release Notes for version 2025.0.0

Axon Server 2025.0 supports seamless integration with non-Axon Framework applications through HTTP(s) and RSocket. This approach eliminates the need for a separate Axon Synapse installation.

Axon Server can perform the following actions:

• route commands and queries to HTTP(s) and RSocket endpoints
• publish events to HTTP(s) and RSocket endpoints (backed by persistent streams)

Clients can now:

• store events and snapshots in Axon Server through a new HTTP(s) operation
• invoke commands and queries through a new HTTP(s) operation
• read aggregate events and snapshots through a new HTTP(s) operation

For more information, check Integrations⁠.

⁠Release Notes for version 2024.2.0

Bug fixes and improvements:

• Improved the stability of changes to cluster topology. When changing cluster topology, e.g., adding or removing nodes from replication groups, previously occurring instabilities have been fixed by revising the implementation of configuration changes.
• Improved performance of message routing with many clients. If the environment contains many client applications (more than 500), there previously were noticeable performance impacts. These have been fixed, and explicit configuration options have been provided.
• All-new AxonServer grafana dashboard. The dashboard we provide for Grafana was completely reworked from scratch to simplify interpretation while at the same time improve accuracy. The new dashboard reflects the new metrics introduced in previous versions.
• Fixed a bug in the search screen, resulting in results from the previous search being mixed with the current one.
• Better integration in Axoniq Console
• Upgraded dependencies. AxonServer was upgraded to the latest dependencies available wherever possible.
• Adding a node with an already existing node name now fails gracefully
• Improved contents of the diagnostics package
• Ephemeral contexts now remove entries from the global index

⁠Release Notes for version 2024.1.0

⁠Persistent streams

Persistent streams provide the option to open an event stream from a client and let Axon Server track the progress. This was already available as a preview version in 2024.0, but is now available by default. Persistent streams are supported in Axon Framework 4.10 as an alternative to tracking or pooled streaming event processors.

For more information see subcribing event processor⁠ in the Axon Framework section.

⁠Bug fixes and improvements

• Prevent stale threads when an Axon Server node closes the connection to another node
• Clean up metrics from disconnected clients
• prevent WARN log messages when a query completed message was received from an unexpected client
• Allow context with ephemeral events without a license
• Fix for listing event processors when there are more than 512 event processors

⁠Docker image changes

The default Java version for the Docker images has changed from Java 11 to Java 17. This means that the docker images with tag "latest", "latest-nonroot", "2024.1.0", and "2024.1.0-nonroot" use Java 17. Java 11 based images are still available with the "-jdk-11" extensions in the tag name.

⁠Dependency updates

• gRPC version updated to 1.65.1

⁠Release Notes for version 2024.0.0

⁠Database Update

Updated H2 database to store the Control DB, addressing some issues from previous H2 version (see the upgrade instructions in https://library.axoniq.io/axon_server_upgrade/upgrading_as_2024.html⁠).

⁠New Features and Improvements

Redesigned User Interface: The UI has been completely revamped with a modern look and feel for a better user experience. The changes include:

• Simplified Overview Page: Access node information easily with filtering and scaling options.
• Dedicated License Page: Track license expiry dates and view available features for non-enterprise users.
• Monitoring Page: View important health information, display logs, and download diagnostic packages.
• System Tasks: List and cancel running system tasks.
• Search Event Store Page: Improved usability with removable columns, formatted code styles, and auto-composable queries.
• Command and Queries Pages: Revamped for a better overview of messages in the system.
• Long-Running Commands Component: View and cancel commands running longer than 1 second.
• Scheduled Events Page: View and cancel scheduled events.
• Streams Page (Experimental): Accessible for persistent streams if dev mode is enabled.
• API Tokens (formerly Applications): Renamed for clarity, with improved token management.
• Support for Wide Screens and Dark/Light Themes: Enhanced viewing experience.
• Connection, Health, and Early Event Processor Issue Detection: Improved issue detection and resolution.
• Embedded Documentation Snippets: Access documentation directly within the UI.

Preview of new persistent streams feature, event streams where Axon Server manages the publication of events to clients and keeps track of the progress. This feature is enabled when development mode is enabled or when axoniq.axonserver.preview.persistent-streams property is set to true.

⁠Release Notes for version 2023.2.0

⁠TLS Certificate and Key Replacement at Runtime

Axon Server now supports the hot (runtime) replacement of certificates and keys used for TLS, eliminating the need for server restarts.

⁠Enhanced Metrics Exposure

We have revamped the metrics exposed by Axon Server for better clarity and comprehensibility. Adhering to the 4 golden signals terminology, metrics are now systematically organized. Users can access both old and new style metrics in this version. However, there’s an option to disable the old style metrics.

⁠Upgraded Diagnostics Package

To aid in issue resolution, Axon Server now provides a more comprehensive diagnostics package. The package now contains more detailed information about raft status. It offers a snapshot of metrics and health information. There’s a listing of files in the replication group. Information about multi-tier storage is included. Logs are included as well.

⁠Other Improvements

• We’ve addressed various security concerns through dependency updates. Additionally, several bugs have been identified and rectified.
• The role ‘MONITOR’ is now granted permission to access the ‘internal/raft/status’ endpoint.
• We’ve transitioned to new versions for some of the external libraries used in Axon Server.

⁠Release Notes for version 2023.1.0

⁠New Features and Enhancements:

⁠Event Transformation

The new Event Transformation feature allows users to perform specific event transformations like updates and deletes in the event store, utilizing the Event Transformation API. This functional change is intended to facilitate more flexible event management in rare instances where modifications are unavoidable.

⁠Forced Client Reconnection

In the application view, users are now provided with an option to force the client to reconnect. This addition aims to offer a practical tool for addressing client connectivity issues.

⁠Node Removal from Cluster

It is now possible to remove a node from the cluster through the user interface (UI). This functionality, previously accessible only via the command-line interface (CLI) and REST API, has been expanded to the UI for broader accessibility.

⁠Temporary Adjustment to Development Mode

In this release, we have temporarily disabled the 'Development Mode/Event Purge' feature. Users should now utilize the 'Delete/Create Context' operation as an alternative. This change will remain in place until a more efficient solution is implemented.

⁠Enhanced Memory Management

In an effort to optimize performance, we have updated Axon Server's approach to memory management for file resources. Prior to this release, Axon Server primarily depended on the Java garbage collector to reclaim memory used by memory-mapped files. With this update, memory management is now undertaken directly by Axon Server, enhancing efficiency in file resource usage.

⁠Bug Fixes

This release also contains fixes for the following issues:

• Replication group creation did not work in conjunction with the HTTPS (-s) option
• Race condition in unregister node leaves node partially in the cluster

⁠Product Updates

⁠Unified Axon Server artifact

The Axon Server artifact has been updated to simplify the deployment process. Instead of separate artifacts for the Axon Server Standard Edition and Enterprise Edition, from now on we are releasing a single artifact. The Axon Server features will adjust automatically based on the presence of a provided license. Note that the Axon Server Standard Edition remains open-source, but separate releases will no longer be made.

Release notes for previous versions can be found in the Release notes section of the reference guide⁠

⁠Running Axon Server

To run Axon Server in Docker, you can use the image provided on Docker Hub:

$ docker run -d --name my-axon-server -p 8024:8024 -p 8124:8124 docker.axoniq.io/axoniq/axonserver
...some container id...

For more information on how to run Axon Server in a Docker/Kubernetes environment, check the reference guide⁠.

⁠Configuring Axon Server

Axon Server uses sensible defaults for all of its settings, so it will actually run fine without any further configuration. However, if you want to make some changes, below are the most common options.

⁠Environment variables for customizing the Docker image of Axon Server

• JAVA_TOOL_OPTIONS

  This is used to pass JVM options. Default is to use it for heap size setting, with "-Xmx512m".

• AXONIQ_AXONSERVER_NAME

  This is the name the Axon Server uses for itself.

• AXONIQ_AXONSERVER_HOSTNAME

  This is the hostname Axon Server communicates to the client as its contact point. Default is "localhost", because Docker generates a random name that is not resolvable outside of the container.

• AXONIQ_AXONSERVER_DOMAIN

  This is the domain Axon Server can suffix the hostname with.

• SERVER_PORT

  This is the port Axon Server uses for its Web GUI and REST API.

• AXONIQ_AXONSERVER_PORT

  This is the gRPC port used by clients to exchange data with the server.

• AXONIQ_AXONSERVER_ACCESSCONTROL_ENABLED

  Setting enabled to true will enable access control.