CA WA Agent SCP Job fails with com.jscape.inet.ssh.protocol.v2.marshaling.PacketCodec$InvalidMacException
search cancel

CA WA Agent SCP Job fails with com.jscape.inet.ssh.protocol.v2.marshaling.PacketCodec$InvalidMacException

book

Article ID: 100029

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent

Issue/Introduction

SCP job type fails with the following message:
02/12/20XX 15:19:09.991-0500 1 FtpPlugin.SCP Transfer thread for 11111.100000_2/
XXXXXX/MAIN.CybSFTPHandler.run[:979] - com.jscape.inet.sftp.SftpException:
com.jscape.inet.ssh.protocol.v2.marshaling.PacketCodec$InvalidMacException
at com.jscape.inet.sftp.SftpException.wrap(Unknown Source)
at com.jscape.inet.sftp.Sftp.a(Unknown Source)
.......
.......
Caused by: com.jscape.inet.ssh.protocol.v2.marshaling.PacketCodec$InvalidMacException: null
at com.jscape.inet.ssh.protocol.v2.marshaling.PacketCodec.c(Unknown Source)
at com.jscape.inet.ssh.protocol.v2.marshaling.PacketCodec.read(Unknown Source)
at com.jscape.inet.ssh.protocol.v2.marshaling.PacketCodec.read(Unknown Source)
at com.jscape.util.l.a.fb.read(Unknown Source)

The "null" is not a valid value, it may mean that the MAC handshaking is failing, possibly due to a timeout.
 

Environment

CA WA Agent 11.3 / 11.4
OS: Any

Cause

The handshaking failure may be due to a read timeout. The connection timeout can been increased.

Resolution

To increase the read timeout to 90 seconds (for example), set the following in the agentparm.txt file and restart the agent:


ftp.scp.sshd.timeout=90000

In 11.4 we need to be at 11.4 SP1 build 1933 to use the above timeout value because of a bug that was present at the 11.4 build 1609

Release notes System Agent 11.4

SYSAGT-320 SFTP Read Timeout Greater Than 30 Seconds Not Used
SFTP read timeout value greater than 30 seconds is not used. Setting the read timeout value for SFTP transfers greater than 30 seconds retains the 30 second timeout.