JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 11

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 12

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Problem: The JOC Cockpit requires to register Agents by their URL, e.g. http://<host>:<port> or https://<host>:<port>. If the wrong URL is specified when registering an Agent, e.g. if the port is wrong or if the hostname is wrong, then the Agent status "Coupling failed" will be reported. When hovering the Agent Status with the mouse then the full error message will be displayed. For example, when using the wrong hostname an error will be displayed such as
    • akka.stream.StreamTcpException: Tcp command [Connect(localhst:5674,None,List(),Some(10 seconds),true)] failed because of java.net.UnknownHostException: localhst [suppressed: TCP Connect localhst:5674: java.net.UnknownHostException: localhst]
    • This error message is available from the Controller's log file too, e.g. from the JS7_CONTROLLER_DATA/logs/controller.log file, see JS7 - Log Files and Locations.



  • Solution: To resolve this error click the "Edit" action menu item for the respective Agent and enter the correct URL for the Agent.

...

  • Problem: After initial operation is successfully completed for an Agent and due to some weird reason the Agent's journal later on is deleted/damaged then this may fail the coupling between Controller and Agent.
    • The JOC Cockpit will report the Agent status "Shutdown". When hovering the Agent Status with the mouse then the full error message will be displayed, for example
      • AgentNotDedicated: This Agent has not been created yet.
  • Solution: This problem can be resolved by restarting the Agent. At the point in time of Agent restart the JOC Cockpit and Controller have to be active and connected. In case that the problem to couple the Agent persists, then re-register the Agent from the JOC Cockpit using the "Edit" action menu and submitting the same settings for the Agent.

...

  • Problem: After successfully completing initial operation of Controller and Agents if due to some weird reason the Controller's journal is deleted/damaged then this may fail the coupling with Agents.
    • The JOC Cockpit will report the Agent status "Shutdown". When hovering the Agent Status with the mouse then the full error message will be displayed, for example 
      • AgentNotDedicated: This Agent has not been created yet.
  • Solution: This problem can be resolved by restarting the Controller. At the point in time of Controller restart the JOC Cockpit and Agents have to be up and running. In case the problem to couple Agents persists re-register the Agents the JOC Cockpit using the Agents' "Edit" action menu.
    • Consider that loss of a Controller's journal includes that
      • any scheduling objects such as workflows have to be re-deployed,
      • any orders of the Daily Plan have to be re-submitted,
      • any currently running orders are lost.
    • Use of a Controller cluster will leverage such a situation as the Secondary Controller operates a synchronized copy of the journal and will pick up operations immediately. The failed Primary Controller can be started later on will automatically synchronize with the Secondary Controller's journal.

...