"Get Call" is included during "SSH Shell"'s sessionId processing, the SSH session is down.
I found a problem that an SSH session will be disconnected if you include a "GetCall" operation in the "SSH Shell" process using session ID.
When processing SSH Shell and get call are executed consecutively, it occurs at random timing.
This event was confirmed when targeting multiple SSH servers. For example, CentOS 6.7, HP-UX 11i v3.
This problem occurs with almost 100% probability in my environment.
But, deleting "Get Call" from "SSH session"'s sessionId processing does not cause this problem.
The operations used are as follows.
/Base [1.9.1]/Library/Operations/Remote Command Execution/SSH/v2.0/SSH Shell Logon
/Base [1.9.1]/Library/Operations/Remote Command Execution/SSH/v2.0/SSH Shell
/Base [1.9.1]/Library/Operations/Remote Command Execution/SSH/v2.0/SSH Shell Logoff
/Base [1.9.1]/Library/Operations/Excel/Get Cell
/Base [1.9.1]/Library/Utility Operations/Looping/Loop
My OO Version is 10.50.
Why does this problem occur?
If you do not specify the following input parameters of the "SSH Shell" step, the operation will be an error because the SSH session can not be used.
If the following input parameters are specified, SSH sessions are created one after another on the destination SSH server.