Uploaded image for project: 'JITL - JobScheduler Integrated Template Library'
  1. JITL - JobScheduler Integrated Template Library
  2. JITL-451

Remove return parameters std_out_output and std_err_output from some JITL Jobs

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 1.11.7, 1.12.2
    • None

    Description

      Current Situation

      • The SSH, SQLPLus and ManagedExecutable Job set order parameters std_out_output and std_err_output with the latest output to stdout or stderr. This can result in errors if the value is too long.
      • An error can be raised as indicated with the SourceForge thread ERRNO-7 Argument list too long
      • The problem is due to the fact that the value of an environment variable should not exceed 128KB which is not guaranteed for this parameter as we cannot know the size of output to stdout / stderr.

      Desired Behavior

      • The parameters will be removed.

      Workaround

      • Create a post-processing script for the SSH job that assigns empty values to both parameters like this:
        <?xml version="1.0" encoding="ISO-8859-1"?>
        <job  title="Launch commands or executable files by SSH" order="yes" stop_on_error="no" name="ssh_job">
            <description >
                <include  file="jobs/JobSchedulerSSHJob.xml"/>
            </description>
        
            <params >
                <param  name="user" value="test"/>
                <param  name="host" value="localhost"/>
                <param  name="command_script" value="echo &quot;hello world&quot;"/>
                <param  name="password" value="test"/>
                <param  name="auth_method" value="password"/>
            </params>
        
            <script  language="java" java_class="sos.scheduler.job.SOSSSHJob2JSAdapter"/>
        
            <monitor  name="drop_parameters" ordering="0">
                <script  language="java:javascript">
                    <![CDATA[
        function spooler_process_after( spooler_process_result )
        {
            spooler_task.order.params.set_var( 'std_out_output', '' );
            spooler_task.order.params.set_var( 'std_err_output', '' );
        
        	return spooler_process_result;
        }
                    ]]>
                </script>
            </monitor>
        
            <run_time />
        </job>
        

      Attachments

        Issue Links

          Activity

            People

              sp Santiago Aucejo Petzoldt
              ap Andreas PĆ¼schel
              Oliver Haufe Oliver Haufe
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: