Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Linux
Description
Current Situation
- No problems on Windows
- When the restart command
<modify_spooler cmd="terminate_and_restart"/>
is called via startscript, JOC or a different http client such as curl then the JobScheduler answers immediately with <ok/> and is shutting down but not started again.
- No error is logged in the scheduler.log
- If the above command is called with the JobScheduler directly via TCP and its command line option -send-cmd then the following error is raised but the JobScheduler restarts.
Error Z-JAVA-105 Java exception java.lang.RuntimeException: Plugin com.sos.scheduler.engine.plugins.newwebservice.NewWebServicePlugin cannot be prepared: java.lang.RuntimeException: Binding to TCP port /0.0.0.0:40411 failed. Port is possibly in use and not available. Switch on DEBUG-level logging for `akka.io.TcpListener` to log the cause. CommandFailed(Bind(Actor[akka://Engine/user/EngineWebServer-http-0.0.0.0:40411#33728034],/0.0.0.0:40411,100,List(),Some(ServerSettings(spray-can/1.3.4,false,1,Timeouts(1441 minutes,1 day,2 s..., method=CallVoidMethodA []
Desired Behavior
The JobScheduler restart command has to work for HTTP
Attachments
Issue Links
- relates to
-
JS-1618 Shell jobs should have an environment with an unchanged LD_LIBRARY_PATH which is modified by the startscript so that the JobScheduler finds some own libraries.
- Released
- links to