Why doesn't the mControl Editor reconnect after I restart the mControl Automation Service?
Background: If the mControl Automation Service has been restarted after failure, the mControl Editor, which is running does not connect to a running mControl service.
Explanation: The mControl Editor may not connect to a restarted server because it may be attempting to connect to a previous mControl Automation Service session. If the previous session ended as a failure, the mControl Editor may take up to 6 minutes to give up on the previous session.
If the mControl Automation Service stops normally, it will signal an end of session to the mControl Editor, ensuring a new session can connect properly.
If, however, the mControl Automation Service exited improperly, the mControl Editor may continue to be connected to the poorly exited service session. The mControl Editor is using a web application that uses a 6-minute heartbeat check to its paired mControl Automation Service session. If the heartbeat fails, mControl Editor will try another two times and if these fail, it will give up on the session and wait for a new session to start.
Workaround: There are essentially two ways to overcome this issue: