History Service and Controller state reset

Current Situation

• The following scenario:
  • Controller and JOC Cockpit History Service are operational.
    • The Controller events are successfully synchronized via the History Service - everything works as expected.
  • Controller is shut down (History Service is active).
  • Controller journal files are deleted (JS7_CONFIG_DIR/state directory).
  • Controller started and a new journal was initialized.
  • After this point:
    • The JS7_CONTROLLER_DATA/logs/controller.log file is "spammed" with messages about the History user's login/logout:

      ... Session:<n> for User:History: Login ...
      ... Session:<n> for User:History: Logout

• • • Controller events are no longer synchronized by the History Service.
      • The History Service does not log errors.
• This behavior can only be identified by analyzing the JS7_CONTROLLER_DATA/logs/controller.log file or if the History Service has not synchronized new job executions.

Desired Behavior

• If the Controller's journal is removed and the Controller is reset then the Proxy Service in JOC Cockpit should reset too and should renew the connection to the Controller. This prevents ongoing retries to login the History Service to the Controller which is performed by the Proxy Service.

Workaround

• Restart History Service if Controller state is reset (journal files deleted).