Observation 7: Agent-initiated file uploads do not reach ThingWorx platform
User Actions
The user must perform the following actions when faced with this error:
• Verify if you created a subscription to monitor FileTransfer events on either the source repository (edge Thing) or the target repository (SystemRepository Thing).
• Check the agent log. If possible, enable debugging log messages at the edge for the agent. Verify if your agent can receive upload file egress from the Connector. Also, verify if the agent can upload chunks without error.
• Check if the upload failed due to a violation of the maximum size of the offline queue used by the File Transfer Subsystem. To do this, review the following configuration settings:
◦ Max File Transfers Allowed in Offline Queue
◦ Max File Transfers Allowed Per Thing in Offline Queue
Additionally, monitor the results of the following FileTransferSubsystem service calls to check if the count reaches the maximum threshold value:
◦ GetQueuedTransferJobCount
◦ GetQueuedTransferJobCountByThing
If the results of the service calls match the maximum limit of the configuration settings limits, then agent-initiated uploads are rejected since the maximum threshold limits are being violated.
• Check if the upload was delayed due to maximum edge-controlled allowed violation of the File Transfer Subsystem service for the ThingWorx Platform. To do this, review the following configuration settings:
◦ Max Edge-Controlled File Transfers Allowed
◦ Max Edge-Controlled File Transfers Allowed Per Thing
◦ Timeout for Edge-Controlled File Transfers
Additionally, monitor the results of the following FileTransferSubsystem service calls to check if the count reaches the maximum threshold allowed or maximum allowed per Thing threshold value:
◦ GetActiveTransferJobs
Determine why transfer jobs are not being completed and eventually timing out, thus delaying the start of agent-initiated file uploads.
Administrator Actions
In addition to the steps that the user performs, the administrator must perform the following steps when faced with this error:
• Check if ThingWorx Platform file repository (SystemRepository) has run out of disk space.
• Verify that you have set the emessage.file-transfer.upload.url connection configuration option to the correct value. The syntax is : https, EXTERNAL host name, port.