Fabric managed broker does not restart after connection to Zookeeper is restored.

Issue

We are running a Fabric managed environment with one or more Fabric containers deploying a broker only.
If the container running the broker looses its connection to the Fabric registry (where the broker is registered in Zookeeper), the broker instance will be shut down (not the container running the broker). This is expected.

However we noticed occasions where the broker was not restarted once the connection to the registry was restored.
This seems to happen mostly when the Zookeeper connection is lost for a rather short time (few seconds only) and restored quickly thereafter.