14
Views
3
Comments
Solved
[Serve files at scale Demo application] Large files don't seem to work
Application Type
Reactive

I have everything set up and working, small files seem to upload fine, but larger files don't seem to work:


https://personal-atnom0y1.outsystemscloud.com/ServeFilesAtScale/Start


Any advice?


Thanks so much

UserImage.jpg
Daniel W
Solution

Ahh there was a max file limit set on the file uploader, all working well now

2021-10-09 07-57-44
Stefan Weber
 
MVP

:-) Yes. Sorry. I haven't thought of that either

2021-10-09 07-57-44
Stefan Weber
 
MVP
Solution

Hi Daniel,

thank you for reading my article and trying out the demo application. Most likely you just hit the default timeout setting of the application. You can change the server timeout setting in service studio, by clicking on the module name.


If you have done that already and you are trying to upload an object which is larger than 5 GB then the OutSystems S3 Connector component (which is also used in the demo) cannot be used. Objects that exceed 5GB have to uploaded in parts which is not supported by the OutSystems Connector. I haven't had that use case myself so i cannot provide a multipart capable connector for that.

There is also a chance that you hit the memory limits of a personal environment. As also for put the whole object must be loaded into memory before it gets sent to S3 via the connector. An alternative solution is to create a presigned URL for PUT operation and use that URL on the frontend to upload an object directly via Javascript.

Hope that helps.

Stefan

UserImage.jpg
Daniel W
Solution

Ahh there was a max file limit set on the file uploader, all working well now

2021-10-09 07-57-44
Stefan Weber
 
MVP

:-) Yes. Sorry. I haven't thought of that either

2021-10-09 07-57-44
Stefan Weber
 
MVP
Solution

Hi Daniel,

thank you for reading my article and trying out the demo application. Most likely you just hit the default timeout setting of the application. You can change the server timeout setting in service studio, by clicking on the module name.


If you have done that already and you are trying to upload an object which is larger than 5 GB then the OutSystems S3 Connector component (which is also used in the demo) cannot be used. Objects that exceed 5GB have to uploaded in parts which is not supported by the OutSystems Connector. I haven't had that use case myself so i cannot provide a multipart capable connector for that.

There is also a chance that you hit the memory limits of a personal environment. As also for put the whole object must be loaded into memory before it gets sent to S3 via the connector. An alternative solution is to create a presigned URL for PUT operation and use that URL on the frontend to upload an object directly via Javascript.

Hope that helps.

Stefan

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.