Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 

Max FileTransfer block size and "Timed out APIRequestMessage" error


Max FileTransfer block size and "Timed out APIRequestMessage" error

I am playing around with the file transfer setting on the remote thing client. I'm seeing slow file transfer so I tried increasing the block size. But when I increase the block size over 32k the transfer starts timing out with message "Timed out APIRequestMessage". I am using SendFile in the .net SDK.

I'm wondering if there are some other setting I'm missing, anyone have insight into this?




Daniel, what's the Max FileTransfer block size set on the FileTransfer Subsystem in the Platform?

It's was at the default 128k, I tried upping it to 1000k but no change.

I believe there was an issue with file transfers when the file size exceeded the block size causing it to time out. What version of the SDK are you using?

Please do note that increasing the block size might impact performance as well.

File size is huge so it's always going to be larger than block size in my case, that seems counter intuitive?

We're on version

Did you find a solution to this?

Using the .NET SDK the default block size was 8000 bytes, so my 400MB download to the asset took 90 min.  I tried increasing the block size, but you cannot do it directly, so I had to shutdown and reinitialize the FTManager, my download shows up for a few seconds, never seeming to transfer any blocks, then disappears. I thought my 10 second timeout on GetFile was too short for larger block sizes, so I increased it to 100 seconds, but still around 10 seconds or so, the active transfer disappears from the FT Subsystem and I have no idea why, no exception is being thrown.


InitializeFileTransferManager(new FileTransferInfo { BlockSize = 128000 });



You can set the FileTransferInfo in the config. I found it also just by accident:


config.FileTransferInfo = new FileTransferInfo { BlockSize = (uint)Math.Pow(2, 15), StagingDir = System.IO.Directory.GetCurrentDirectory() + "/staging", Timeout = 60000, MaxFileSize = 1024000000, MD5BlockSize = (ushort)6400 };

But you have to fiddle around with the BlockSize. I found out that the java sdk uses blockSize 65536 (2^16). But if you set it too high you will get Timeouts (Timed out APIRequestMessage). Not sure why. Locally it is working with 2^15 - ^16 will timeout.