Connector Exception 12: File Upload Failure — Max Offline Queue Size Violation on the ThingWorx Platform
If you notice that file uploads are not arriving at ThingWorx Platform, you may have encountered this issue. This exception indicates that thee maximum size of the offline queue for file transfer jobs has been exceeded, so no additional file transfer jobs can be placed in the queue. For more information, refer to
Observation 7: Agent-initiated file uploads do not reach ThingWorx Platform.
To simulate this situation, the following scenario was used:
1. Start ThingWorx Platform.
2. Start eMessage Connector.
3. Change the configuration of the ThingWorx File Transfer Subsystem such that the maximum number of file transfers allowed in the offline queue is 1 (the default setting is 50,000).
4. Use the Copy service of the File Transfer Subsystem to enqueue one file transfer job for an Axeda Thing that is not connected.
5. Start an agent that is configured to send a file upload request.
In this scenario, ThingWorx Platform rejects the request from eMessage Connector to enqueue the file transfer because the maximum number of file transfer jobs allowed in the queue has been reached (step4). Here are some lines from the error that is logged at the Connector:
...[NettyClient-NIO-5] ERROR c.t.p.e.s.f.UploadFileServiceImpl -
Error detected when calling Copy() when processing agent upload request
com.Thingworx.sdk.api.concurrent.RequestException: Server returned an error with status
STATUS_INTERNAL_ERROR and message: 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, jobTid=<job_id>
...