updated links

Author: KarlErickson

articles/spring-apps/.openpublishing.redirection.spring-apps.json

@@ -212,7 +212,12 @@
         },
         {
             "source_path": "concepts-for-java-memory-management.md",
-            "redirect_url": "/azure/spring-apps/enterprise/concepts-for-java-memory-management",
+            "redirect_url": "/azure/spring-apps/basic-standard/concepts-for-java-memory-management",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "enterprise/concepts-for-java-memory-management.md",
+            "redirect_url": "/azure/spring-apps/basic-standard/concepts-for-java-memory-management",
             "redirect_document_id": true
         },
         {

articles/spring-apps/basic-standard/concepts-for-java-memory-management.md

@@ -6,7 +6,7 @@ author: KarlErickson
 ms.author: kaiqianyang
 ms.service: spring-apps
 ms.topic: conceptual
-ms.date: 06/27/2024
+ms.date: 07/30/2024
 ms.custom: devx-track-java, devx-track-extended-java
 ---
 
@@ -27,7 +27,7 @@ A Java application's memory has several parts, and there are different ways to d
 
 Heap memory stores all class instances and arrays. Each Java virtual machine (JVM) has only one heap area, which is shared among threads.
 
-Spring Boot Actuator can observe the value of heap memory. Spring Boot Actuator takes the heap value as part of `jvm.memory.used/committed/max`. For more information, see the [jvm.memory.used/committed/max](tools-to-troubleshoot-memory-issues.md#jvmmemoryusedcommittedmax) section in [Tools to troubleshoot memory issues](tools-to-troubleshoot-memory-issues.md).
+Spring Boot Actuator can observe the value of heap memory. Spring Boot Actuator takes the heap value as part of `jvm.memory.used/committed/max`. For more information, see the [jvm.memory.used/committed/max](../enterprise/tools-to-troubleshoot-memory-issues.md#jvmmemoryusedcommittedmax) section in [Tools to troubleshoot memory issues](../enterprise/tools-to-troubleshoot-memory-issues.md).
 
 Heap memory is divided into *young generation* and *old generation*. These terms are described in the following list, along with related terms.
 
@@ -72,7 +72,7 @@ Full GC or major GC does garbage collection in the entire heap. Full GC can also
 
 The maximum heap size influences the frequency of minor GC and full GC. The maximum metaspace and maximum direct memory size influence full GC.
 
-When you set the maximum heap size to a lower value, garbage collections occur more frequently, which slow the app a little, but better limits the memory usage. When you set the maximum heap size to a higher value, garbage collections occur less frequently, which may create more out-of-memory (OOM) risk. For more information, see the [Types of out-of-memory issues](how-to-fix-app-restart-issues-caused-by-out-of-memory.md#types-of-out-of-memory-issues) section of [App restart issues caused by out-of-memory issues](how-to-fix-app-restart-issues-caused-by-out-of-memory.md).
+When you set the maximum heap size to a lower value, garbage collections occur more frequently, which slow the app a little, but better limits the memory usage. When you set the maximum heap size to a higher value, garbage collections occur less frequently, which may create more out-of-memory (OOM) risk. For more information, see the [Types of out-of-memory issues](../enterprise/how-to-fix-app-restart-issues-caused-by-out-of-memory.md#types-of-out-of-memory-issues) section of [App restart issues caused by out-of-memory issues](../enterprise/how-to-fix-app-restart-issues-caused-by-out-of-memory.md).
 
 Metaspace and direct memory can be collected only by full GC. When metaspace or direct memory is full, full GC will occur.
 
@@ -86,7 +86,7 @@ Applications in Azure Spring Apps run in container environments. For more inform
 
 ### Important JVM options
 
-You can configure the maximum size of each part of memory by using JVM options. You can set JVM options by using Azure CLI commands or through the Azure portal. For more information, see the [Modify configurations to fix problems](tools-to-troubleshoot-memory-issues.md#modify-configurations-to-fix-problems) section of [Tools to troubleshoot memory issues](tools-to-troubleshoot-memory-issues.md).
+You can configure the maximum size of each part of memory by using JVM options. You can set JVM options by using Azure CLI commands or through the Azure portal. For more information, see the [Modify configurations to fix problems](../enterprise/tools-to-troubleshoot-memory-issues.md#modify-configurations-to-fix-problems) section of [Tools to troubleshoot memory issues](../enterprise/tools-to-troubleshoot-memory-issues.md).
 
 The following list describes the JVM options:
 
@@ -156,9 +156,9 @@ Overall, when configuring maximum memory sizes, you should consider the usage of
 
 ## Java OOM
 
-OOM means the application is out of memory. There are two different concepts: container OOM and JVM OOM. 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).
+OOM means the application is out of memory. There are two different concepts: container OOM and JVM OOM. For more information, see [App restart issues caused by out-of-memory issues](../enterprise/how-to-fix-app-restart-issues-caused-by-out-of-memory.md).
 
 ## See also
 
-- [App restart issues caused by out-of-memory issues](how-to-fix-app-restart-issues-caused-by-out-of-memory.md)
-- [Tools to troubleshoot memory issues](tools-to-troubleshoot-memory-issues.md)
+- [App restart issues caused by out-of-memory issues](../enterprise/how-to-fix-app-restart-issues-caused-by-out-of-memory.md)
+- [Tools to troubleshoot memory issues](../enterprise/tools-to-troubleshoot-memory-issues.md)

articles/spring-apps/basic-standard/toc.yml

@@ -69,7 +69,7 @@ items:
   - name: Memory
     items:
     - name: Java memory management
-      href: ../enterprise/concepts-for-java-memory-management.md?toc=/azure/spring-apps/basic-standard/toc.json&bc=/azure/spring-apps/basic-standard/breadcrumb/toc.json
+      href: concepts-for-java-memory-management.md
     - name: Tools to troubleshoot memory issues
       href: ../enterprise/tools-to-troubleshoot-memory-issues.md?toc=/azure/spring-apps/basic-standard/toc.json&bc=/azure/spring-apps/basic-standard/breadcrumb/toc.json
     - name: Fix app restart issues caused by OOM

articles/spring-apps/consumption-dedicated/index.yml

@@ -95,7 +95,7 @@ landingContent:
       - linkListType: concept
         links:
           - text: Java memory management
-            url: ../enterprise/concepts-for-java-memory-management.md?toc=/azure/spring-apps/consumption-dedicated/toc.json&bc=/azure/spring-apps/consumption-dedicated/breadcrumb/toc.json
+            url: ../basic-standard/concepts-for-java-memory-management.md?toc=/azure/spring-apps/consumption-dedicated/toc.json&bc=/azure/spring-apps/consumption-dedicated/breadcrumb/toc.json
       - linkListType: quickstart
         links:
           - text: Analyze logs and metrics

articles/spring-apps/consumption-dedicated/toc.yml

@@ -53,7 +53,7 @@ items:
   - name: Memory
     items:
     - name: Java memory management
-      href: ../enterprise/concepts-for-java-memory-management.md?toc=/azure/spring-apps/consumption-dedicated/toc.json&bc=/azure/spring-apps/consumption-dedicated/breadcrumb/toc.json
+      href: ../basic-standard/concepts-for-java-memory-management.md?toc=/azure/spring-apps/consumption-dedicated/toc.json&bc=/azure/spring-apps/consumption-dedicated/breadcrumb/toc.json
     - name: Tools to troubleshoot memory issues
       href: ../enterprise/tools-to-troubleshoot-memory-issues.md?toc=/azure/spring-apps/consumption-dedicated/toc.json&bc=/azure/spring-apps/consumption-dedicated/breadcrumb/toc.json
     - name: Fix app restart issues caused by OOM

articles/spring-apps/enterprise/how-to-fix-app-restart-issues-caused-by-out-of-memory.md

@@ -43,7 +43,7 @@ The **Resource health** page on the Azure portal shows app restart events due to
 
 The metrics *App memory Usage*, `jvm.memory.used`, and `jvm.memory.committed` provide a view of memory usage. For more information, see the [Metrics](tools-to-troubleshoot-memory-issues.md#metrics) section of [Tools to troubleshoot memory issues](tools-to-troubleshoot-memory-issues.md). Configure the maximum memory sizes in JVM options to ensure that memory is under the limit.
 
-The sum of the maximum memory sizes of all the parts in the [Java memory model](concepts-for-java-memory-management.md#java-memory-model) should be less than the real available app memory. To set your maximum memory sizes, see the typical memory layout described in the [Memory usage layout](concepts-for-java-memory-management.md#memory-usage-layout) section of [Java memory management](concepts-for-java-memory-management.md).
+The sum of the maximum memory sizes of all the parts in the [Java memory model](../basic-standard/concepts-for-java-memory-management.md#java-memory-model) should be less than the real available app memory. To set your maximum memory sizes, see the typical memory layout described in the [Memory usage layout](../basic-standard/concepts-for-java-memory-management.md#memory-usage-layout) section of [Java memory management](../basic-standard/concepts-for-java-memory-management.md).
 
 Find a balance when you set the maximum memory size. When you set the maximum memory size too high, there's a risk of container OOM. When you set the maximum memory size too low, there's a risk of JVM OOM, and garbage collection will be of and will slow down the app.
 
@@ -70,5 +70,5 @@ Metaspace memory is usually stable.
 
 ## See also
 
-- [Java memory management](concepts-for-java-memory-management.md)
+- [Java memory management](../basic-standard/concepts-for-java-memory-management.md)
 - [Tools to troubleshoot memory issues](tools-to-troubleshoot-memory-issues.md)

articles/spring-apps/enterprise/index.yml

@@ -112,10 +112,6 @@ landingContent:
         url: structured-app-log.md
       - text: Analyze logs and metrics
         url: diagnostic-services.md
-    - linkListType: concept
-      links:
-      - text: Java memory management
-        url: concepts-for-java-memory-management.md
 
   # Card (optional)
   - title: Secure apps

articles/spring-apps/enterprise/toc.yml

@@ -82,8 +82,6 @@ items:
     href: concept-app-status.md
   - name: Memory
     items:
-    - name: Java memory management
-      href: concepts-for-java-memory-management.md
     - name: Tools to troubleshoot memory issues
       href: tools-to-troubleshoot-memory-issues.md
     - name: Fix app restart issues caused by OOM

articles/spring-apps/enterprise/tools-to-troubleshoot-memory-issues.md

@@ -57,7 +57,7 @@ App memory usage is a percentage equal to the app memory used divided by the app
 
 For JVM memory, there are three metrics: `jvm.memory.used`, `jvm.memory.committed`, and `jvm.memory.max`, which are described in the following list.
 
-"JVM memory" isn't a clearly defined concept. Here, `jvm.memory` is the sum of [heap memory](concepts-for-java-memory-management.md#heap-memory) and former permGen part of [non-heap memory](concepts-for-java-memory-management.md#non-heap-memory). JVM memory doesn't include direct memory or other memory like the thread stack. Spring Boot Actuator gathers these three metrics and determines the scope of `jvm.memory`.
+"JVM memory" isn't a clearly defined concept. Here, `jvm.memory` is the sum of [heap memory](../basic-standard/concepts-for-java-memory-management.md#heap-memory) and former permGen part of [non-heap memory](../basic-standard/concepts-for-java-memory-management.md#non-heap-memory). JVM memory doesn't include direct memory or other memory like the thread stack. Spring Boot Actuator gathers these three metrics and determines the scope of `jvm.memory`.
 
 - `jvm.memory.used` is the amount of used JVM memory, including used heap memory and used former permGen in non-heap memory.
 
@@ -69,13 +69,13 @@ For JVM memory, there are three metrics: `jvm.memory.used`, `jvm.memory.committe
 
 - `jvm.memory.max` is the maximum amount of JVM memory, not to be confused with the real available amount.
 
-  The value of `jvm.memory.max` can sometimes be confusing because it can be much higher than the available app memory. To clarify, `jvm.memory.max` is the sum of all maximum sizes of heap memory and the former permGen part of [non-heap memory](concepts-for-java-memory-management.md#non-heap-memory), regardless of the real available memory. For example, if an app is set with 1 GB of memory in the Azure Spring Apps portal, then the default heap memory size is 0.5 GB. For more information, see the [Default maximum heap size](concepts-for-java-memory-management.md#default-maximum-heap-size) section of [Java memory management](concepts-for-java-memory-management.md).
+  The value of `jvm.memory.max` can sometimes be confusing because it can be much higher than the available app memory. To clarify, `jvm.memory.max` is the sum of all maximum sizes of heap memory and the former permGen part of [non-heap memory](../basic-standard/concepts-for-java-memory-management.md#non-heap-memory), regardless of the real available memory. For example, if an app is set with 1 GB of memory in the Azure Spring Apps portal, then the default heap memory size is 0.5 GB. For more information, see the [Default maximum heap size](../basic-standard/concepts-for-java-memory-management.md#default-maximum-heap-size) section of [Java memory management](../basic-standard/concepts-for-java-memory-management.md).
 
   If the default *compressed class space* size is 1 GB, then the value of `jvm.memory.max` is larger than 1.5 GB regardless of whether the app memory size 1 GB. For more information, see [Java Platform, Standard Edition HotSpot Virtual Machine Garbage Collection Tuning Guide: Other Considerations](https://docs.oracle.com/javase/9/gctuning/other-considerations.htm) in the Oracle documentation.
 
 #### jvm.gc.memory.allocated/promoted
 
-These two metrics are for observing Java garbage collection (GC). For more information, see the [Java garbage collection](concepts-for-java-memory-management.md#java-garbage-collection) section of [Java memory management](concepts-for-java-memory-management.md). The maximum heap size influences the frequency of minor GC and full GC. The maximum metaspace and maximum direct memory size influence full GC. If you want to adjust the frequency of garbage collection, consider modifying the following maximum memory sizes.
+These two metrics are for observing Java garbage collection (GC). For more information, see the [Java garbage collection](../basic-standard/concepts-for-java-memory-management.md#java-garbage-collection) section of [Java memory management](../basic-standard/concepts-for-java-memory-management.md). The maximum heap size influences the frequency of minor GC and full GC. The maximum metaspace and maximum direct memory size influence full GC. If you want to adjust the frequency of garbage collection, consider modifying the following maximum memory sizes.
 
 - `jvm.gc.memory.allocated` is the amount of increase in the size of the young generation memory pool after one GC and before the next. This value reflects minor GC.
 
@@ -97,7 +97,7 @@ For more information, see [Capture heap dump and thread dump manually and use Ja
 
 ## Modify configurations to fix problems
 
-Some issues you might identify include [container OOM](how-to-fix-app-restart-issues-caused-by-out-of-memory.md#fix-app-restart-issues-due-to-oom), heap memory that's too large, and abnormal garbage collection. If you identify any of these issues, you may need to configure the maximum memory size in the JVM options. For more information, see the [Important JVM options](concepts-for-java-memory-management.md#important-jvm-options) section of [Java memory management](concepts-for-java-memory-management.md#important-jvm-options).
+Some issues you might identify include [container OOM](how-to-fix-app-restart-issues-caused-by-out-of-memory.md#fix-app-restart-issues-due-to-oom), heap memory that's too large, and abnormal garbage collection. If you identify any of these issues, you may need to configure the maximum memory size in the JVM options. For more information, see the [Important JVM options](../basic-standard/concepts-for-java-memory-management.md#important-jvm-options) section of [Java memory management](../basic-standard/concepts-for-java-memory-management.md#important-jvm-options).
 
 You can modify the JVM options by using the Azure portal or the Azure CLI.
 
@@ -124,5 +124,5 @@ az spring app update \
 
 ## See also
 
-- [Java memory management](concepts-for-java-memory-management.md)
+- [Java memory management](../basic-standard/concepts-for-java-memory-management.md)
 - [App restart issues caused by out-of-memory issues](how-to-fix-app-restart-issues-caused-by-out-of-memory.md)

articles/spring-apps/index.yml

@@ -135,9 +135,6 @@ conceptualContent:
             - text: Use custom DNS names
               url: enterprise/how-to-custom-domain.md
               itemType: how-to-guide
-            - text: Java memory management
-              url: enterprise/concepts-for-java-memory-management.md
-              itemType: concept
             - text: Use structured application logs
               url: enterprise/structured-app-log.md
               itemType: how-to-guide
@@ -327,7 +324,7 @@ conceptualContent:
         - title: Manage and monitor apps
           links:
             - text: Java memory management
-              url: enterprise/concepts-for-java-memory-management.md?toc=/azure/spring-apps/consumption-dedicated/toc.json&bc=/azure/spring-apps/consumption-dedicated/breadcrumb/toc.json
+              url: basic-standard/concepts-for-java-memory-management.md?toc=/azure/spring-apps/consumption-dedicated/toc.json&bc=/azure/spring-apps/consumption-dedicated/breadcrumb/toc.json
               itemType: concept
             - text: Analyze logs and metrics
               url: consumption-dedicated/quickstart-analyze-logs-and-metrics-standard-consumption.md