[#215] Fix: Reverse Component Deregistration Order in AxonServerTenantProvider

[schananas]

Originally issue is reported here as issue with shutdown handler introduction. After reproducing the issue, its found that issue is actually in AxonServerTenantProvider shutdown method.

Problem

The current implementation of the shutdown() method in AxonServerTenantProvider deregisters components in the same order they were registered. This can lead to potential issues during application shutdown, as components that depend on others might be deregistered before the components they depend on.

Solution

This PR modifies the shutdown() method to deregister components in the reverse order of their registration. This ensures that components are shut down in a proper sequence, allowing for any necessary cleanup operations to occur in the correct order.

Changes

1. Modified the shutdown() method in AxonServerTenantProvider:

   • Now reverses the list of registrations for each tenant before cancelling them.
   • This ensures that the last registered component is the first to be deregistered.

2. Added unit tests to verify the correct shutdown order.

3. Updated JavaDoc for the shutdown() method to reflect its behavior and intended use.

Testing

• Added new unit test whenShutdownThenDeregisterComponentsInReverseOrder() to verify the correct deregistration order.

This PR resolves #215.

[CLAassistant]

All committers have signed the CLA.

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
87.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[smcvb]

Looks good to me 👍