Currently, if there is exchanges still in the queue of the DeliveryChannel when a SU Provides after shut down (i.e., after its endpoint is deactived from the container POV), these messages are simply lost.
Like with PETALSESBCONT-379, for the new exchanges (those that are not answers to previous exchanges), it would make sense to reinject them in the router because:
- either there is other provider that can answer them.
- either there is not and the consumer should get an error for its request.
For non-new exchanges, they should still be handled by the component.
After undeploy, an error should be returned to the sender.
This goes in the way to improve the reliability of the container for message delivery (PETALSDISTRIB-146).
Improvement Request
Resolved
Major
