Throwing CommandExecutionException triggers a AxonServerRemoteCommandHandlingException

[felipeplets]

When throwing a CommandExecutionException the expected behavior is that my method decorated with @ExceptionHandler(CommandExecutionException.class) is called.

But once I've added the tracing extension as a dependency instead the AxonServerRemoteCommandHandlingException is triggered thus not reaching my handler.

Creating another handler to AxonServerRemoteCommandHandlingException is not a possibility as I need the getDetails for my use case.

[smcvb]

So, @felipeplets, the time has finally come that we had a look at this.
To be very honest, I am not completely sure whether this is truly originating just through the fact of introducing the Tracing Extension at this moment.
However, you have reported this with a reason, so something must be amiss (or unclear in the reference guide).

To help us underway it would be highly beneficial if you could provide a small sample project which does the following:

1. A vanilla Axon component (no use extensions or Axon Server) which dispatchs a command on the DefaultCommandGateway, which results in a CommandExecutionException.
2. An Axon component which wraps the DefaultCommandGateway in the TracingCommandGateway, showing a different form of exception (likely an instance of RuntimeException.

Thanks in advance @felipeplets, let us know once you have such a small sample in place!

[smcvb]

Closing this issue due to inactivity. Feel free to start the conversation again as soon as your tie allows it @felipeplets.