Recovery and restart for transfers to and from Connect:Direct nodes
WebSphere® MQ Managed File Transfer might be unable to connect to your IBM® Sterling Connect:Direct® node during a transfer; for example, if the node becomes unavailable. Either WebSphere MQ Managed File Transfer attempts to recover the transfer, or the transfer fails and an error message is produced.
If the Connect:Direct node becomes unavailable
- If WebSphere MQ Managed File Transfer has not previously successfully connected to the Connect:Direct node as part of this transfer request, the transfer is tried again for a length of time determined by the values of the cdMaxConnectionRetries and recoverableTransferRetryInterval properties. These properties are specified in the agent.properties file for the Connect:Direct bridge agent. The transfer fails, and an error message is produced, after the number of failed attempts reaches the value of the cdMaxConnectionRetries property. By default, the transfer is attempted indefinitely, with 60 seconds between attempts.
- If WebSphere MQ Managed File Transfer has previously successfully connected to the Connect:Direct node as part of this transfer request, the transfer is tried again for a length of time determined by the values of the cdMaxPartialWorkConnectionRetries and recoverableTransferRetryInterval properties. The transfer fails, and an error message is produced, after the number of failed attempts reaches the value of the cdMaxPartialWorkConnectionRetries property. By default, the transfer is attempted indefinitely, with 60 seconds between attempts.
- For certain types of Connect:Direct node failure,
for example the node being forcibly stopped, Connect:Direct processes go into
Held Due to Error (HE)status when the node recovers. After the node recovers, WebSphere MQ Managed File Transfer automatically resumes any Connect:Direct processes that are related to the file transfer and have a status ofHE. - If the transfer fails, any temporary files relating to the transfer are deleted from the system that hosts the Connect:Direct bridge. The location of these temporary files is defined by the cdTmpDir property.
- If the transfer is from WebSphere MQ Managed File Transfer to Connect:Direct, and a source disposition of delete is specified, then the source files are not deleted if the transfer fails.
If the Connect:Direct node user credentials are invalid
If WebSphere MQ Managed File Transfer fails to connect to the Connect:Direct node because the credentials of the user are rejected by the node, the transfer fails and an error message is produced. In this situation, check that you have provided the correct user credentials for the Connect:Direct node. For more information, see Mapping credentials for Connect:Direct.
If the Connect:Direct bridge agent becomes unavailable
If the Connect:Direct bridge agent becomes unavailable, any ongoing file transfers recover in the same way as standard WebSphere MQ Managed File Transfer transfers. For more information, see Recovery and restart for WebSphere MQ Managed File Transfer.