ThingWorx Exception 3: File upload failure due to maximum offline queue size per Thing violation
This exception appears if file uploads that are initiated by the agent do not reach ThingWorx Platform. A symptom could be violation of the value of the maximum offline queue size per Thing configured for the File Transfer Subsystem Copy service in ThingWorx.
Here is a scenario that will result in this exception:
1. Start ThingWorx Platform.
2. Start eMessage Connector.
3. Modify the Max File Transfers Allowed Per Thing in Offline Queue configuration setting of the File Transfer Subsystem service of the ThingWorx Platform from 10 to 1.
4. Start the agent that sent 2 upload requests for 2 different files.
In this scenario, ThingWorx Platform rejects the request of the eMessage Connector to enqueue the file transfer and the following error is logged:
...[context: Unable to enqueue file transfer since offline queue for the Thing is full.
maxQueuePerThingSize=1, ThingName=Weather1, ...
[message: Unable to enqueue file transfer since offline queue for the Thing is full.
maxQueuePerThingSize=1, ThingName=Weather1, ...
Unable to dispatch [ uri = /Subsystems/FileTransferSubsystem/Services/Copy/]:
Unable to Invoke Service Copy on FileTransferSubsystem :
Unable to enqueue file transfer since offline queue for the Thing is full.
maxQueuePerThingSize=1, ThingName=Weather1, ...
error executing APIRequest Message: Unable to dispatch [ uri = /Subsystems