Internal Server Error Error HTTP Status: 500 while uploading big size assets | Community
Skip to main content
serenapitotti
serenapitotti
Level 2
March 11, 2022
Solved

Internal Server Error Error HTTP Status: 500 while uploading big size assets

  • March 11, 2022
  • 1 reply
  • 2368 views

Hi,

we have the need to upload many assets with an external tool that connects to AEM and sends them via API.

We didn't have any issue till we tried to upload files over 500MB, that are needed for very high resolution printings. When we try to upload that TIF pictures, on the client side we have this error:

 

Error code: ERROR_HTTP_STATUS_NOT_OK Error Description: Internal Server Error Error HTTP Status: 500

 

Then, checking on AEM we found no errors, but with the logs we understood that the upload servlet crashes when accessing the file parameter sent by the client (accessing the parameters array this way: params[0], even if the first parameter exists).

 

Since we tried this upload also with a local environment of AEM, and we had no error there, we thought that maybe the problem is something about allocated memory for uploading assets. We also tried to increase the "Max Memory" in OSGi configuration "Day CQ DAM Buffered Image Cache" to 1073741824 (1GB, and it was set at 500MB), then restarted author instance, but with no effect.

Thanks,
Serena

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Anmol_Bhardwaj

    Hi @serenapitotti ,

     

    Try overlaying the node in 

    /libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/fileupload

    and increasing the max upload limit. 

     

    Also, if you're trying to upload assets through a browser, there is a limit set by the browser as well. So using external tool would be recommended

    1 reply

    Anmol_Bhardwaj
    Community Advisor
    Anmol_BhardwajCommunity AdvisorAccepted solution
    Community Advisor
    March 21, 2022

    Hi @serenapitotti ,

     

    Try overlaying the node in 

    /libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/fileupload

    and increasing the max upload limit. 

     

    Also, if you're trying to upload assets through a browser, there is a limit set by the browser as well. So using external tool would be recommended

      Terms & ConditionsAccessibility statement

      Loading footer...