Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.10
Description
Current Situation
- If a Master before 1.10 contacts the JobScheduler Universal Agent then the task log contains:
015-09-20 20:23:21.287+0100 [ERROR] Z-JAVA-105 Java exception spray.httpx.UnsuccessfulResponseException: Status: 404 Not Found
2015-09-20 20:23:21.287+0100 [ERROR] Body: The requested resource could not be found., method=CallObjectMethodA []
2015-09-20 20:23:21.287+0100 [ERROR] SCHEDULER-280 Process terminated with exit code 1 (0x1)
2015-09-20 20:23:21.287+0100 [info] SCHEDULER-918 state=closed
2015-09-20 20:23:21.302+0100 [info] SCHEDULER-962 Protocol ends in C:/ProgramData/sos-berlin.com/jobscheduler/desktop-pu80tpk_4444/logs/task.job2 - The Agent log does update with the following:
2015-09-20 20:23:21,231 +0100 [DEBUG] akka.io.TcpListener - New connection accepted
2015-09-20 20:23:21,245 +0100 [DEBUG] spray.can.server.HttpServerConnection - Dispatching POST request to http://192.168.0.199:4445/jobscheduler/engine/command to handler Actorakka://JobScheduler-Agent/system/IO-TCP/selectors/$a/3#1201787827 - Effectively the only means to decide that the Agent was contacted by an older Master release is the use of a URL such as http://192.168.0.199:4445/jobscheduler/engine/command
Feature
- JobScheduler Universal Agent should raise a clearly defined error message when being contacted by a Master released before 1.10
Attachments
Issue Links
- mentioned in
-
Page Loading...