Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
1.12.10, 1.13.0
-
None
Description
Current Situation
When starting an SSH Job on the Master on a centos 7 linux machine, the SSH Job fails with the error:
COM-80020009 DISP_E_EXCEPTION [step] [] [Z-JAVA-105 Java exception java.lang.NoSuchMethodError: com.jcraft.jsch.agentproxy.connector.SSHAgentConnector.isConnectorAvailable(Ljava/lang/String;)Z, method=spooler_process()Z [], in Remote_module_instance_server::step], method=call
Desired Behavior
The SSH Job should run on linux without an error.
Maintainer Note
The error occurs because unfortunately an old jar file, which is not needed anymore, was deployed with this release.
The jsch-agent-proxy-0.0.4.jar has been replaced by jsch.agentproxy.core-0.0.9.jar and jsch.agentproxy.sshagent-0.0.9.jar.
The error has occurred on a CentOS 7 Linux system, but not on an Ubuntu test system.
More important for the occurance of this error is the order in which the files are read by the class loader of the java version used. This can depend on the sorting order of the operating system.
Workaround
Remove the jsch-agent-proxy-0.0.4.jar file from [SCHEDULER_HOME]/lib/3rd-party.
Download and add jsch.agentproxy.jsch-0.0.9.jar to the [SCHEDULER_HOME]/lib/3rd-party folder.
Attachments
Issue Links
- relates to
-
JITL-571 SSH Job SOSSSHJob2JSAdapter always uses Key Agent when publickey is used as authentication method
- Released