As an administrator, I want to have the IG notification service more resilient to disconnections, in order to not restart the route in case of websocket connection failures
As of today (IG 6.0/6.1), when the AmService cannot create the web-socket connection to receive live notifications, the whole route startup fails, that's easy to spot, but if the disconnection happen after the route startup, then the subscription fails (more or less silently) and no further notifications are received.
That is likely to lead to inconsistent cache content (as we rely on notifications to eagerly evict cache entries).
- Support transparent reconnection in case of broken connections
- Delay between retries has to be configurable (with a default value of 5s)