Compatibility with YADE 1.x branches — Transfer via Jump Host to Target using CheckSize

Current Behavior:

In YADE 1.x, the CheckSize setting applied to all transfer nodes involved in a Jump Host transfer (Source → Jump Host as well as Jump Host → Target).

In the JS7 YADE 2.x branch, when CheckSize=false is configured for a file transfer via a Jump Host, the setting is not applied to all transfer nodes.
For a transfer using Source → Jump Host → Target, the CheckSize setting is applied only to the Jump Host → Target transfer, while the intermediate Source → Jump Host transfer performs its own independent file-size validation.

If the file sizes differ between the Source and Jump Host, the transfer fails with a YADEEngineTransferFileSizeException indicating that the file size does not match. 

Desired Behavior:

The CheckSize setting must be applied to all transfer nodes involved in a Jump Host transfer, matching the YADE 1.x behavior.

Patch

• A cumulative patch is available for JS7 version 2.8.3.
  • The patch includes YADE-659 and the the fixes for YADE-652, YADE-653.
  • Download: js7_agent.2.8.3-PATCH.YADE-659.jar [ sha256 ] [ sig ] [ tsr ]
  • Applying the patch
    • Since YADE-626, YADE can be executed not only as a standalone Shell Job, but also as an integrated Java JITL Job.
    • This means the patch can/should be deployed in two locations:
      • <agent install>/lib/patches - for YADE configured as a JITL Job (com.sos.jitl.jobs.yade.YADEJob)
        • See JS7 - Patches for Agent
        • Note: The Agent instance has to be restarted to apply patch.
      • <agent install>/yade/lib/patches - for YADE configured as a Shell Job
        • Note: The Agent instance does not need to be restarted to apply the patch
    • Note YADE-659
      • The YADE-659 fix provided with the patch must be applied to the JS7 YADE client. Applying the YADE-659 fix to the YADE Jump Host client is not required.