4.5
Getting Started
Axon Framework
Axon Server
Error Codes
This page depicts the various Error codes that Axon Server will return in the case of any problems while Processing Client Requests / Message Handling / Administrative Tasks / Cluster Errors.
Area
Error Code
Description
Client Request Processing Errors
​
​
​
AXONIQ-1000
AUTHENTICATION_TOKEN_MISSING
This indicates that the Axon Server has been configured with authentication enabled and a client application did not pass a token.
​
AXONIQ-1001
AUTHENTICATION_INVALID_TOKEN
This indicates that the Axon Server has been configured with authentication enabled and a client application has supplied an invalid token.
​
AXONIQ-1002
UNSUPPORTED_INSTRUCTION
This error is returned when the Axon Server cannot recognize the instruction passed to it.
​
AXONIQ-1003
INSTRUCTION_EXECUTION_ERROR
This error is returned when the Axon Server throws an error during the execution of the instruction passed to it.
​
AXONIQ-1004
INSTRUCTION_RESULT_TIMEOUT
This indicates that the execution of the instruction did not finish within the timeout set.
​
AXONIQ-1100
NODE_IS_REPLICA
This error is returned when a request from a node to join a cluster is received by a node that is no longer leader.
Normally the node would forward the request to the leader, but if there is a leader change during the processing of the join request this may happen.
​
AXONIQ-1300
NO_SUCH_APPLICATION
This error is returned when any client sends any instruction with a specific application name that has not been registered with Axon Server.
​
AXONIQ-1301
NO_SUCH_NODE
This error is returned when any client sends any instruction with a specific node name that has not been registered with Axon Server.
​
AXONIQ-1302
CONTEXT_NOT_FOUND
This error is returned when any client sends any instruction with a specific context that has not been registered with Axon Server.
​
AXONIQ-1304
CONTEXT_EXISTS
This error is returned when there is an instruction to create a specific context within Axon Server and it already exists.
​
AXONIQ-1400
NO_AXONSERVER_FOR_CONTEXT
This error is returned when there is no Axon Server node available for the specified context.
​
AXONIQ-1500
AXONSERVER_NODE_NOT_CONNECTED
This error is returned when there is an instruction to create a specific context within Axon Server and it already exists.
Input Errors
​
​
​
AXONIQ-2000
INVALID_SEQUENCE
This error is returned when there is a gap between the sequence number for a particular aggregate instance that the client application sends and the current sequence number for that instance in the Axon Server Event Store.
​
AXONIQ-2001
PAYLOAD_TOO_LARGE
This error is returned when the payload for the message to be executed is too large.
​
AXONIQ-2002
TOO_MANY_EVENTS
This error is returned when an ad-hoc query (e.g. from the Search Page) has buffered too many rows to send to the client, this error also is returned when a single transaction from a client contains more than 32767 events (due to a limitation in the event store format, we can only store MAX_SHORT events in a single transaction).
​
AXONIQ-2100
NO_LEADER_AVAILABLE
This error is returned when no leader is available to execute any instruction sent to the Axon Server cluster.
​
AXONIQ-2101
NOT_RUNNING_IN_CLUSTER
This error is returned when Axon Server is not running in a cluster.
​
AXONIQ-2102
CONTEXT_UPDATE_IN_PROGRESS
This error is returned when an instruction on a specific context is rejected as it might be undergoing an update.
Last modified 3mo ago
Copy link