Subscription query throws INTERNAL: AXONIQ-5000 exception after Axon Server restart

We are using a subscription query to push changes to our front-end. Sometimes we restart Axon Server with our service still running. When our service reconnects to Axon Server it tries to start the subscription query again but then we start seeing AXONIQ-5000 errors. If we then restart the service then the error no longer apears and everything is working fine again.

Is there a way to recover from this error, without restarting the service?

We are using Axon Framework 4.5.3 (the behaviour is the same with 4.5.4) and server 4.5.10

Is this service a long-running (hot) stream? Also, do you see any error in the log because of getting AXONIQ-5000?

You could wrap the initialization of the subscription query into Mono.fromCallable and pair it with retry() operator, and when an error happens it will retry with a brand new subscription query connection.

Thanks, I will try the mono suggestion and report back.

It is indeed long-running. We have a front-end that is calling the subscription query via a fetch request. The result of the subscription query is converted into a sever sent event stream. When axon server shuts down, the front-end stops the request. But when the page is reload is does the request again. As soon as that happens the below exception shows up in a loop in the log. Nothing else.

2022-03-14 11:51:45.170 ERROR 18148 --- [ault-executor-6] s.a.p.b.t.s.TimelineEventListenerUseCase : Error while streaming timeline messages

org.axonframework.axonserver.connector.AxonServerException: INTERNAL: AXONIQ-5000
	at org.axonframework.axonserver.connector.ErrorCode.lambda$static$24( ~[axon-server-connector-4.5.8.jar:4.5.8]
	at org.axonframework.axonserver.connector.ErrorCode.convert( ~[axon-server-connector-4.5.8.jar:4.5.8]
	at org.axonframework.axonserver.connector.ErrorCode.convert( ~[axon-server-connector-4.5.8.jar:4.5.8]
	at org.axonframework.axonserver.connector.ErrorCode.convert( ~[axon-server-connector-4.5.8.jar:4.5.8]
	at org.axonframework.axonserver.connector.event.util.GrpcExceptionParser.parse( ~[axon-server-connector-4.5.8.jar:4.5.8]
	at reactor.core.publisher.Mono.lambda$onErrorMap$31( ~[reactor-core-3.4.13.jar:3.4.13]
	at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onError( ~[reactor-core-3.4.13.jar:3.4.13]
	at reactor.core.publisher.MonoCompletionStage.lambda$subscribe$0( ~[reactor-core-3.4.13.jar:3.4.13]
	at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete( ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire( ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture.postComplete( ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture.completeExceptionally( ~[na:na]
	at io.axoniq.axonserver.connector.query.impl.SubscriptionQueryStream.onError( ~[axonserver-connector-java-4.5.4.jar:4.5.4]
	at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose( ~[grpc-stub-1.43.0.jar:1.43.0]
	at io.grpc.internal.ClientCallImpl.closeObserver( ~[grpc-core-1.43.0.jar:1.43.0]
	at io.grpc.internal.ClientCallImpl.access$300( ~[grpc-core-1.43.0.jar:1.43.0]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal( ~[grpc-core-1.43.0.jar:1.43.0]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext( ~[grpc-core-1.43.0.jar:1.43.0]
	at ~[grpc-core-1.43.0.jar:1.43.0]
	at ~[grpc-core-1.43.0.jar:1.43.0]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker( ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$ ~[na:na]
	at java.base/ ~[na:na]

2022-03-14 11:51:45.172 ERROR 18148 --- [ault-executor-6] e.b.s.c.GlobalControllerExceptionHandler : org.axonframework.axonserver.connector.AxonServerException: INTERNAL: AXONIQ-5000

And when you restart Axon Server do you see query (handler) listed as registered in the dashboard?

You may also upgrade to Axon Framework 4.5.8, that’s the latest version.

We have two query handlers, but after restart the query handlers do not show anymore.

does the issue still persist?

It does indeed.

Adding the Mono.fromCallable doesn’t seem to change the behaviour. I tried to create a sample application to reproduce the issue. However, in the sample the issue doesn’t appear.

It’s a bit of a puzzle now what’s the real problem.

I realized that we have a fetch running in the browser, if an error occurs during the fetch it will do the request again. If the fetch happens when Axon server is shutdown then you will be able to reproduce the error.

I have create an example application that can trigger the error:

These are the steps:

  1. Start the application
  2. Do a request to localhost:8080. This will output an server sent event stream, emitting 100 random uuid, once per second
  3. Shut down Axon Server, application will error with unable to connect to Axon server
  4. Do a request to localhost:8080. This will produce an error 500
  5. Start Axon Server
  6. Do a request to localhost:8080, this will produce an concurrency exception (optional, depends on timing)
  7. Do another request to localhost:8080, this will produce an AXONIQ-5000 exception.

Sounds like a bug, will investigate…
Can you try one more thing: on the Axon Server node that is connected to your client application execute this API requestReconnect ,this will force reconnection and hopefully it can fix the problem.


It seems that my Axon Server doesn’t have swagger ui. I checked the docs, but those are also referring to swagger.

I’m running the standard Axon Server SE docker container. Is there another way to access swagger?

Hi @jaco,

I believe the swagger url changed on new versions!
You might be able to find it under http://localhost:8024/swagger-ui/index.html#/


Thank you. I have the swagger ui working.

Executing that call resolves the problem. So it’s a good work around for now.