Error: Transfer did not complete within 60000 ms
A file transfer may fail for connectivity reasons. If the Azure IoT Hub Connector loses the connection with the configured Azure Storage Container in the middle of executing a File Transfer job, the file transfer job times out and the transfer fails. The following error appears in the ThingWorx Platform Error Log:
2019-08-06 10:49:20.146-0400 [L: ERROR] [O: E.c.t.l.f.RedirectLogFilter]
[I: ] [U: Administrator] [S: ] [P: ]
[T: FileTransfer-3734b78b-394d-42df-a4b7-480461f2b562-2]
[context: Transfer did not complete within 60000 ms:
job=TransferJob [tid: 624267a6-d3ac-4c93-8c9a-9c61f789ea4e,
sourceRepo: SystemRepository, sourcePath: /large.bin,
targetRepo: azurefilerepository, targetPath: /large.bin,
partPath: /large.bin.azurefilerepository.part,
sourceChecksum: 7583b57452ccb83f9d313ab76e3629b8,
targetChecksum: , state: CANCELLED,
code: 504, message: Transfer did not complete within 60000 ms,
isAsync: false, isRestartEnabled: true, isComplete: false,
bytesTransferred: 49664000, blockcount: 388, blocksize: 128000,
size: 512000000, maxsize: 10000000000, transferTime: 59967,
transferControl: platform, reservationId: ,
user: Administrator, isQueueable: false, enqueueTime: 0,
enqueueCount: 0, metadata: null,
Job [id: 624267a6-d3ac-4c93-8c9a-9c61f789ea4e, lastTouch: 1565102960146,
timeout: 30000, TimedLock [createTime: 1565102900109,
signalTime: 1565102960109, duration: 60000, signaled: true]]]]
[message: Transfer did not complete within 60000 ms]
2019-08-06 10:49:20.146-0400 [L: ERROR] [O: E.c.t.s.s.f.e.FileCopyTask] [I: ]
[U: Administrator] [S: ] [P: ]
[T: FileTransfer-3734b78b-394d-42df-a4b7-480461f2b562-2]
[context: Transfer did not complete within 60000 ms:
job=TransferJob [tid: 624267a6-d3ac-4c93-8c9a-9c61f789ea4e,
sourceRepo: SystemRepository, sourcePath: /large.bin,
targetRepo: azurefilerepository, targetPath: /large.bin,
partPath: /large.bin.azurefilerepository.part,
sourceChecksum: 7583b57452ccb83f9d313ab76e3629b8, targetChecksum: ,
state: CANCELLED, code: 504, message: Transfer did not complete within 60000 ms,
isAsync: false, isRestartEnabled: true, isComplete: false,
bytesTransferred: 49664000, blockcount: 388, blocksize: 128000,
size: 512000000, maxsize: 10000000000, transferTime: 59967,
transferControl: platform, reservationId: , user: Administrator,
isQueueable: false, enqueueTime: 0, enqueueCount: 0,
metadata: null,
Job [id: 624267a6-d3ac-4c93-8c9a-9c61f789ea4e,
lastTouch: 1565102960146, timeout: 30000, TimedLock [createTime: 1565102900109,
signalTime: 1565102960109, duration: 60000, signaled: true]]]][
message: Transfer did not complete within 60000 ms]
com.thingworx.system.subsystems.filetransfer.engine.TransferException:
Transfer did not complete within 60000 ms
at com.thingworx.system.subsystems.filetransfer.engine.
TransferTask.checkState(TransferTask.java:107)
at com.thingworx.system.subsystems.filetransfer.engine.
FileTransferTask.read(FileTransferTask.java:392)
at com.thingworx.system.subsystems.filetransfer.engine.
FileCopyTask.execute(FileCopyTask.java:134)
at com.thingworx.system.subsystems.filetransfer.engine.
FileTransferTask.runImpl(FileTransferTask.java:166)
at com.thingworx.system.subsystems.filetransfer.engine.
TransferTask.run(TransferTask.java:57)
at java.util.concurrent.ThreadPoolExecutor.
runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.
run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Solutions
Check your network for possible outages or traffic bottlenecks and address them. If necessary, restart the Connector.
Also, make sure that the configuration of the Blob Storage is correct in the AzureIotHub Thing in ThingWorx. In ThingWorx Composer, navigate to the AzureIotHub Thing to be sure that the following properties are set correctly for the AzureBlobStorageTemplate Thing:
• The accountName of the AzureBlobStorageTemplate Thing
• The connection string of the AzureBlobStorageTemplate Thing
If you change the configuration, you MUST restart the Connector.