...

• Problem: When adding the URL for an Agent frequent misconfigurations include
  • use of the wrong URL protocol:
    • the protocol for the URL is added as HTTP when the Agent is operated for HTTPS or
    • the URL is added as HTTPS when the Agent is operated for HTTP.
  • The JOC Cockpit will report the Agent status as "Coupling failed". When hovering the Agent Status with the mouse then the full error message will be displayed, for example
    • java.net.ssl.SSLException: Unrecognized SSL message
    • 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 modify the protocol for the Agent.

...

• Problem: When an Agent is already registered with JOC Cockpit and the same URL is used for the registration of another Agent with a new Agent ID then an error occurs.
  •  The term "same URL" can include literally different URLs that point to the same host and network address.
    • As JOC Cockpit is not directly connected to Agents (for the purpose of optionally being operated in a different network zone) but refers to Agents by use of a Controller, therefore host name resolution (DNS) as available for the Controller applies.
    • If a proxy service is in place when using the Agent URL then the proxy could route different URLs to the same Agent.
  • The JOC Cockpit will report the Agent status being "Reset". When hovering the Agent Status with the mouse then the full error message will be displayed, for example
    • AgentPathMismatch: This is the 'primary_agent' agent, not: secondary_agent agent
    • The error message indicates that the Agent has been registered with the Agent ID primary_agent and that the user tries to register a second Agent with the same URL and the Agent ID secondary_agent.
    • 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 assign the correct URL for the Agent secondary_agent. If the intention is to replace the Agent primary_agent by the Agent secondary_agent then first delete the Agent primary_agent and then register the Agent secondary_agent with the JOC Cockpit.

...

• 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 instance operates a synchronized copy of the journal and will pick up operations immediately during fail-over (3-5s). The failed Primary Controller instance can be started later on and will automatically synchronize with the Secondary Controller instance's journal.

Further Information

...