While File Transfer running, if “Renew transfer key” launched the File Transfer hangs on Windows Agent
Article ID: 88047
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
GSS connection not ready, message will be discarded.
If a File Transfer (FT), using FT_VERSION=1, is started between two Agents, and on the target Agent the Transfer key of the Agent is renewed, the FT will not deliver any messages back to the Automation Engine (AE), and will hang in an active status.
This error occurs if the target Agent is a Windows Agent.
Investigation
After the "Renew transfer key" the Automation Engine (AE) sends the CONNECT messages without GSS token. The Agent does not handle CONNECT messages without GSS token correctly, sending the FT_RECV message ends with the error message "GSS connection not ready, message will be discarded", and the FT gets a status of ENDED_NOT_OK when the destination Agent closes the connection due to a timeout.
GSS connection not ready, message will be discarded.
If a File Transfer (FT), using FT_VERSION=1, is started between two Agents, and on the target Agent the Transfer key of the Agent is renewed, the FT will not deliver any messages back to the Automation Engine (AE), and will hang in an active status.
This error occurs if the target Agent is a Windows Agent.
Investigation
- Use FT_VERSION=1
- Start the FT between 2 Agents with the target using a Windows Agent
- On the Windows target Agent "Renew transfer key"
After the "Renew transfer key" the Automation Engine (AE) sends the CONNECT messages without GSS token. The Agent does not handle CONNECT messages without GSS token correctly, sending the FT_RECV message ends with the error message "GSS connection not ready, message will be discarded", and the FT gets a status of ENDED_NOT_OK when the destination Agent closes the connection due to a timeout.
Cause
Cause type:
Defect
Root Cause: After the "Renew transfer key" the Automation Engine (AE) sends the CONNECT messages without GSS token, and since the Agent doesn't handle CONNECT messages without GSS token correctly, seding the FT_RECV message ends with errors.
Defect
Root Cause: After the "Renew transfer key" the Automation Engine (AE) sends the CONNECT messages without GSS token, and since the Agent doesn't handle CONNECT messages without GSS token correctly, seding the FT_RECV message ends with errors.
Environment
OS: Windows
OS Version: N/A
OS Version: N/A
Resolution
Update to a fix version listed below or a newer version if available.
Fix Status: Fixed
Fix Version(s):
Component(s): Agent Windows
Automation Engine 12.1.0 - Available
Automation Engine 12.0.3 - Available
Automation Engine 11.2.6 - Available
Additional Information
Workaround :
Avoid renewing the transfer key while a File Transfer is running on the Agent.
Avoid renewing the transfer key while a File Transfer is running on the Agent.
Feedback
Yes
No
Powered by
