ThingWorx Exception 2: File upload failure due to maximum offline queue size violation
This exception appears if file uploads that are initiated by the agent do not reach ThingWorx Platform. A symptom could be maximum offline queue size violation of the File Transfer Subsystem service for the ThingWorx Platform.
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 in Offline Queue configuration setting of the File Transfer Subsystem service of the ThingWorx Platform from 50,000 to 1.
4. Enqueue 1 file transfer for an edge Thing that is not connected (via the Copy service of the File Transfer Subsystem).
5. Start the agent that sent the upload request for a file.
In this scenario, ThingWorx Platform rejects the request of the eMessage Connector to enqueue the file transfer and log the following exceptions:
...
[context: Unable to enqueue file transfer since the queue is full
maxQueueSize=1, ThingName=Weather1, ...
Unable to enqueue file transfer since the queue is full
maxQueueSize=1, ThingName=Weather1, ...
Unable to dispatch [ uri = /Subsystems/FileTransferSubsystem/Services/Copy/]:
Unable to Invoke Service Copy on FileTransferSubsystem :
Unable to enqueue file transfer since the queue is full
maxQueueSize=1, ThingName=Weather1, ...
error executing APIRequest Message: Unable to dispatch [ uri = /Subsystems
Was this helpful?