Merge pull request #250717 from yilims/exitcode

fix doc for exit code 137

Author: prmerger-automator[bot]

articles/spring-apps/troubleshoot-exit-code.md

@@ -14,7 +14,7 @@ ms.custom: devx-track-java
 > [!NOTE]
 > Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.
 
-**This article applies to:** ✔️ Basic/Standard ✔️ Enterprise
+**This article applies to:** ✔️ Enterprise ✔️ Basic/Standard
 
 This article describes troubleshooting actions you can take when your application in Azure Spring Apps exits with an error code. You may receive an error code if your application deployment is unsuccessful, or if the application exits when it's running.
 
@@ -44,12 +44,15 @@ The exit code indicates the reason the application terminated. The following lis
 
   - If your application is a static file or dynamic front-end application served by a web server, see the [Common build and deployment errors](how-to-enterprise-deploy-static-file.md#common-build-and-deployment-errors) section of [Deploy web static files](how-to-enterprise-deploy-static-file.md).
 
-- **137** - The application exited because of an out-of-memory error. The application requested resources that the hosting platform failed to provide. Update your application's Java Virtual Machine (JVM) parameters to restrict resource usage or scale up application resources.
-  
-  If the application is a Java application, check the JVM parameter values. They may exceed the memory limit of your application.
+- **137** - The application is terminated immediately by the hosting platform with no grace period. This exit code can be the result of one of the following scenarios:
+
+  - When the liveness check fails, the hosting platform  immediately kills the application after attempting to terminate it and waiting for a grace period. Ensure that your application handles graceful shutdown correctly.
+  - The application exited because of an out-of-memory error. The application requested resources that the hosting platform failed to provide. Update your application's Java Virtual Machine (JVM) parameters to restrict resource usage or to scale up application resources.
+
+    If the application is a Java application, check the JVM parameter values. They may exceed the memory limit of your application.
+
+    For example, suppose you set the *Xmx* JVM parameter to 10 GB, but the application is using up to 5 GB of memory. Decrease the *Xmx* value or increase the application memory to make sure that the value of the *Xmx* parameter is lower or equal to the memory limit of the application.
 
-  For example, suppose you set the *Xmx* JVM parameter to 10 GB, but the application is using up to 5 GB of memory. Decrease the *Xmx* value or increase the application memory to make sure that the value of the *Xmx* parameter is lower or equal to the memory limit of the application.
-  
 - **143** - The application exited because it failed to respond to a health check due to an out-of-memory error or some other error.
 
   This error code is most often generated by an out-of-memory error. For more information, see [App restart issues caused by out-of-memory issues](./how-to-fix-app-restart-issues-caused-by-out-of-memory.md).