Dspace Getting Down frequently

[Raja muthukrishnan Ramanujam]

Hello Team,

We have used Dspace 7.2 back-end and frond-end, When we are trying to access in browser, frequently its getting down...

Frond-End logs:

ERROR RangeError: Maximum call stack size exceeded
    at String.replace (<anonymous>)
    at trimLeft (/app/dist/server/main.js:3:1694982)
    at extractProtocol (/app/dist/server/main.js:3:1696047)
    at new Url (/app/dist/server/main.js:3:1697171)
    at Url (/app/dist/server/main.js:3:1696882)
    at getEmbedSizeParams (/app/dist/server/main.js:3:6000023)
    at DspaceRestResponseParsingService.process (/app/dist/server/main.js:3:5599415)
    at /app/dist/server/main.js:3:5601079
    at Array.forEach (<anonymous>)
    at DspaceRestResponseParsingService.process (/app/dist/server/main.js:3:5601037)
Error:  HttpErrorResponse {
  headers: HttpHeaders {
    normalizedNames: Map(0) {},
    lazyUpdate: null,
    headers: Map(0) {}
  },

Regards,

Raja

[DSpace Community]

Hi Raja,

Unfortunately this error is not providing us enough information to help.  It's difficult to say what could be going on.  You may wish to check our troubleshooting guide for tips on looking for other errors that may be occurring in either the frontend or backend. https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

If no additional errors can be found, then you may want to look also for clues as to what may be going on with the system when this error occurs. For instance, check your Apache logs (if you have Apache as a proxy) to see if you are being crawled by a highly active or bad behaving web spider or similar.

We also have some performance tuning tips for both the frontend & backend in our documentation at https://wiki.lyrasis.org/display/DSDOC7x/Performance+Tuning+DSpace

I would also **highly recommend** considering an upgrade to the latest version of DSpace 7 (currently 7.6.1).  There have been a large number of performance enhancements and feature additions since that 7.2 release.  It's very possible that, if you upgrade, these issues may also go away.

Tim