Exited with status 137 (out of memory), reason: CRASHED

[ramveer64]

The Tomcat server hosting the application is crashing approximately every 30–40 minutes with the following observations:

• Error:  8 May 2025, 17:10:36 (GMT+05:30) audit.app.process.crash web instance: XXXXXX-10f4-411e-5eb0-0e20, index: 0, cell_id: 22ddeb5b-85dc-4188-81ba-70747cf2634c, reason: CRASHED, exit_description: APP/PROC/WEB: Exited with status 137 (out of memory), crash_count: 1, crash_timestamp: 1746704436099938800, version: xxxxxx-e188-48f9-a66d-88efc1122bf2 8 May 2025, 17:08:40 (GMT+05:30) app.crash questionnaire-service-xxxxxx-8b72-xxxx-ddf4-ac7552db702f instance: xxxxxx-7695-4e50-5e5a-06ec, index: 1, cell_id: 872b3d88-3e59-40d6-801b-8d62310a94f0, exit_description: APP/PROC/WEB: Exited with status 137 (out of memory), reason: CRASHED

• Thread count: ~600 active threads

• Heap usage: ~600 MB (as per heap dump analysis)

• Environment Details:

  • RAM: 2 GB

  • Disk Space: 1 GB

  • Number of environments running in parallel: 5

[Willem_Pardaens]

Have a look at the documentation here: https://help.sap.com/docs/btp/sap-business-technology-platform/customizing-java-virtual-machine-jvm-... to look at various options. Last resort is to increase the RAM allocation to the application.