Unable to Catch AggregateDeletedException When Using CommandGateway about axonframework

[smcvb]

The key is in the RemoteHandlingException you receive. This signals you are using either the JGroups or Spring Cloud Extension to distribute your application.

Whenever you are in a distributed environment, you need to assume the scenario that not all instances are equal.

Differently put, some applications may have command handlers, others may not (in short, a heterogeneous system).

Due to this, there is a window of opportunity that the exception thrown one application X does not exist on application Y.
As such, Axon Framework defaults to protect everybody by assuming the exception is unknown, by wrapping it for you.

If you want some level of control over what the exception result is, your best step forward is to throw a dedicated CommandExecutionException, wherein you set the details field.
This field is intended to carry your "exceptional API," enabling you to have conscious exceptional communication between your nodes, instead of assuming the exceptional classes are present on All instances that will ever dispatch commands to said application.

Thus, your best bet is to catch the exception and transform it into a CommandExecutionException with (if necessary) your own details in it.
Granted, Axon Framework could be able to capture the exceptions originating from itself to generate these details.

By the way, you can also check our reference guide on the subject, over here.

I will close this issue as resolved, as I think the predicament is sufficiently addressed.
If you feel differently, be sure to reach out! We're always open for reconsidering.

Lastly, I strongly recommend you upgrade to a more recent version of Axon Framework.
We are already at 4.9.0, with 4.9.1 coming out soon.