Improvement of Issue: "Termine/Restart works but shows ugly error messages"

Current Situation

• The issue JOC-249 is solved with the effect that too many exceptions are not displayed in the JOC Cockpit GUI.

Desired Behavior

• Changes in the JOC Cockpit GUI caused by JOC-249 should be reset.
• If the JobScheduler Master is restarted then the JobScheduler's new web server resets all http connections.
• The JOC web service such as ./process_classes asks the JobScheduler Master for information via the new web server and if it is called asynchronously by JOC Cockpit while the JobScheduler Master is restarted then the ./process_classes web service receives the answer from the JobScheduler Master:

  com.sos.scheduler.engine.common.async.CallQueue$ClosedException: CallQueue is closed. 'TimedCall 'com.sos.scheduler.engine.kernel.DirectSchedulerClient$$anonfun$respondWithSnapshotFuture$1 <function0>'' is rejected
  

• The solution should be implemented with the JOC Cockpit web services.
• The above error from the JobScheduler has to raise a JobSchedulerResetConnectionException instead of a JobSchedulerBadRequestException.
  The web services should catch the JobSchedulerResetConnectionException and send the error with HTTP code 434.
  This HTTP code was introduced for exceptions which are logged but not dispayed with the JOC Cockpit GUI