Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
Current Behavior
If you have a "nested" job chain where you skip all nodes (of the inner job chains) then the JobScheduler crashes
.14 11:45:54.656 scheduler 0 41880.9FF0 1687.848MB .{scheduler} Execute <job_chain_node.modify action="next_state" job_chain="/test/nested2" state="start"/> .14 11:45:54.657 scheduler 0 41880.9FF0 1687.848MB .{scheduler.mainlog} [info] SCHEDULER-965 Executing command <job_chain_node.modify action="next_state" job_chain="/test/nested2" state="start"/> .14 11:45:54.657 scheduler 0 41880.9FF0 1687.848MB .{scheduler} job_chain::Node test/nested2:2 set_action next_state .14 11:45:54.658 scheduler 0 41880.9FF0 1687.848MB .{scheduler.mainlog} [debug9] (Order_queue test/nested2:start) remove_order Order test/nested2:master .14 11:45:54.658 scheduler 0 41880.9FF0 1687.848MB .{scheduler.mainlog} [info] (Order test/nested2:master) set_state success, at=never .14 11:45:54.667 scheduler 15 41880.9FF0 1687.848MB .{scheduler.mainlog} [info] (Order test/nested2:master) SCHEDULER-940 Removing order from job chain .14 11:45:54.667 scheduler 0 41880.9FF0 1687.848MB .{scheduler.order} sos::scheduler::Standard_job::on_order_possibly_available .14 11:45:54.667 scheduler 0 41880.9FF0 1687.848MB .{scheduler.mainlog} [info] (Order master) SCHEDULER-944 End state reached - order will be repeated at 2038-01-19 03:14:07.000Z with state=100 .14 11:45:54.667 scheduler 0 41880.9FF0 1687.848MB .{scheduler.mainlog} [info] (Order master) SCHEDULER-862 Continuing in 'Job_chain /test/nested1' .14 11:45:54.667 scheduler 0 41880.9FF0 1687.848MB .{scheduler.mainlog} [info] (Order master) SCHEDULER-862 Continuing in 'Job_chain /test/nested2' .14 11:45:54.688 scheduler 16 41880.9FF0 1697.625MB . .14 11:45:54.688 scheduler 0 41880.9FF0 1697.625MB .******* ~Sos_self_deleting mit 3 Referenzen ******* .14 11:45:54.688 scheduler 0 41880.9FF0 1697.625MB . .14 11:45:54.835 scheduler 4609 13256.33F4 1542.324MB .{socket.recv} pid=0 recv(1212,size=50000) ret=-1 err=10054 .14 11:45:54.835 scheduler 0 13256.33F4 1542.324MB .[ERROR WINSOCK-10054 WSAECONNRESET - Connection reset by peer [recv]] .14 11:45:54.869 scheduler 31 13256.33F4 1542.324MB .[ERROR WINSOCK-10054 WSAECONNRESET - Connection reset by peer [recv]] .14 11:45:54.869 scheduler 0 13256.33F4 1542.324MB .[xc.append "pid=0"] .14 11:45:54.895 scheduler 16 13256.33F4 1542.324MB .pid=0 Open objects: .14 11:45:54.895 scheduler 0 13256.33F4 1542.324MB .221E903D.00000003 - 0000000002563518 sos::scheduler::com_objects::Com_task_proxy -> sos::scheduler::com_objects::Com_task .14 11:45:54.895 scheduler 0 13256.33F4 1542.324MB .467F743F.00000001 - 000000000251BBF0 sos::scheduler::Com_remote_module_instance_server .14 11:45:54.895 scheduler 0 13256.33F4 1542.324MB .4F6B650B.00000002 - 0000000002543560 zschimmer::com::object_server::Proxy -> sos::scheduler::com_objects::Com_job .14 11:45:54.895 scheduler 0 13256.33F4 1542.324MB .62E86535.00000001 - 000000000251B5E8 sos::scheduler::com_objects::Com_spooler_proxy -> sos::scheduler::com_objects::Com_spooler .14 11:45:54.895 scheduler 0 13256.33F4 1542.324MB .6B84B69A.00000004 - 0000000002581CD0 sos::scheduler::com_objects::Com_log_proxy -> sos::scheduler::com_objects::Com_log .14 11:45:54.895 scheduler 0 13256.33F4 1542.324MB . .14 11:45:54.900 scheduler 16 13256.33F4 1542.324MB {socket} closesocket(1212) ==> 0 .14 11:45:54.900 scheduler 0 13256.33F4 1542.324MB {scheduler} WINSOCK-10054 WSAECONNRESET - Connection reset by peer [recv] / pid=0 .14 11:45:54.900 scheduler 0 13256.33F4 1542.324MB {env} SetEnvironmentVariable("LD_LIBRARY_PATH","")
Desired Behavior
Although it does not make much sense to skip all nodes, the JobScheduler should not crash.