Connector Exception 11: File Upload Failure — Target Repository Out of Disk Space
This Connector exception appears if file uploads that were initiated by the Axeda agent or by the ThingWorx Platform are not showing up in their target destinations,. For more information, refer to
Observation 7: Agent-initiated file uploads do not reach ThingWorx Platform and
Observation 8: Platform-initiated file uploads do not reach ThingWorx Platform.
Here is a scenario that could result in this exception being thrown:
1. Start ThingWorx Platform.
2. Start eMessage Connector.
3. Create a file system to simulate a disk full scenario and pointed SystemRepository to this filesystem.
4. Start an agent that sent an upload request for a large uncompressed file (10M)
...[NettyClient-NIO-4] ERROR c.t.p.e.handlers.UploadHandler -
Error detected while uploading chunk=position=0 total=22105353
targetFile=/uploads/Weather1/
large.txt targetRepo=SystemRepository checksum=...
modelNumber=WeatherModel serialNumber=Weather1
compression=none
... Server returned an error with status STATUS_INTERNAL_ERROR and message:
Unable to dispatch [ uri = ... :
Unable to Invoke Service CreateBinaryFile on SystemRepository :
Unable to Create File [/uploads/Weather1/large.txt]