After an upgrade AW_SFTP jobs go into a running state and remain there.

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Error Message Details:
In the Master's RmiServer log :
MasterSocketManager$_A: doRun 0 SeqNo 94 Agent BDBP Master null service broadcasterror Method null [ErrorMsg: AwE-9999 Internal error (10/5/10 10:19 AM)
Details: com/jcraft/jsch/S]
With AgentService debug enabled you will see the following error in the AgentServices debug log:
AwE-9999
ErrorMsg: AwE-9999 Internal eraror (10/6/10 12:19 PM)
Details: null
java.lang.NoSuchMethodError: com/jcraft/jsch/Session.setConfig(Ljava/lang/String;Ljava/lang/String;)V
 at com.appworx.agent.B.?(Sftp.java:798)
 at com.appworx.agent.B.?(Sftp.java:244)
 at com.appworx.agent.B.<init>(Sftp.java:196)

---

Symptoms
After upgrading to AM v8.0 AW_SFTP jobs go into a running state and seem to hang.

---

Cause
Old files left over from a previous version may not have been cleaned up during the upgrade from the web/classes directory (commons-net-1.4.1.jar & jsch-0.1.29.jar) which is causing AW_SFTP jobs to hang.

---

startso all

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

This issue was resolved with the release of Applications Manger v8.0 SP5 (Bug 26398).

---

Workaround
Remove the following old files if they exist:
$AW_HOME/web/classes/commons-net-1.4.1.jar
$AW_HOME/web/classes/jsch-0.1.29.jar
For the Applications Manager instance to recognize these changes, you will need to stop and restart the Master and Remote Agent by executing the following commands:

     . site/sosite
      stopso all
      startso all