Connector Exception 15: File Download Chunk Failure Due to File Deletion
If an agent cannot download a file and that file download was initiated at ThingWorx Platform, this exception is generated. For more information, refer to
Observation 9: Platform-initiated file downloads are not downloaded by asset.
The following scenario results in this exception:
1. Start ThingWorx Platform.
2. Start eMessage Connector.
3. Make sure that the agent on the related device is not running.
4. Call the Copy service of the File Transfer Subsystem and set queueable to true to initiate a file download.
5. Start the agent. The agent polls ThingWorx Platform, checking for egress messages.
In this scenario, the call to download a chunk of the file from the eMessage Connector fails because the file was deleted. The error message that is logged includes the following lines:
... [NettyClient-NIO-3]
ERROR c.t.p.e.handlers.DownloadHandler -
Failed to read from binary file
com.Thingworx.sdk.api.concurrent.RequestException:
Server returned an error with status STATUS_INTERNAL_ERROR
and message: Unable to dispatch [ uri = ...:
Unable to Invoke Service ReadFromBinaryFile on
SystemRepository : File Does Not Exist