What to do if you think that your file transfer is stuck

On a heavily loaded system or when there are network problems between the source and destination agents, transfers can occasionally appear to be stuck in a queued or recovering state. There are a number of factors that can cause this.

1. Use the ftePingAgent command, or in the IBM MQ Explorer Agents panel right-click on the agent name and select Ping, to check whether the source and destination agents are active and responding to new requests. Look at the agent logs to see if there is a current network connection problem.
2. Check whether the destination agent is running at capacity. It might be that there are numerous source agents all requesting file transfers to the same destination agent. Use the fteShowAgentDetails command with the -v (verbose) parameter, or in the IBM MQ Explorer Agents panel right-click on the agent name and select Properties, to see the current transfer activity for an agent. If the number of running destination transfers is at or close to the agent's maximum number of destination transfers, that can explain why some transfers for source agents appear to be stuck.
3. Transfers to and from protocol bridge agents enter a recovering state if there is a problem contacting the protocol file server. Look at the agent logs to see if there is a current connection problem.
4. Transfers are processed by an agent in priority order. Therefore in a loaded system, a low-priority transfer can remain in the queued state for some time while the agent is loaded with higher priority transfers. Eventually a low-priority transfer is started if that transfer has been queued for a while, even though there are newer higher priority transfers.

Parent topic: MFT general troubleshooting