Recovery and restart for WebSphere MQ File Transfer Edition
If your agent or queue manager are unavailable for any reason, for example because of a power or network failure, WebSphere® MQ File Transfer Edition recovers as follows in these scenarios:
- Typically, if there is a problem while a file is in the process of being transferred, WebSphere MQ File Transfer Edition recovers and restarts that file transfer after the problem is repaired.
- If a file that was in the process of being transferred is deleted or changed while the agent or queue manager are unavailable, the transfer fails and you get a message in the transfer log that provides details about the failure.
- If an agent process fails during a file transfer, the transfer continues when you restart the agent.
- If an agent loses the connection to its agent queue manager, the agent waits in an infinite loop trying to reconnect to the queue manager. When the agent successfully reconnects to its queue manager, the current transfer continues.
- If the agent is stopped for any reason, any resource monitors associated with an agent stops polling. When the agent recovers, the monitors are also restarted, and resource polling resumes.
You can check the status of your transfers in the WebSphere MQ Explorer. If any transfers appear as Stalled, you might need to take corrective action because the stalled status denotes an issue either with the agent or between the two agents involved in the transfer.