Skip to content

Commit 70cfe84

Browse files
committed
nit
1 parent 1a64aed commit 70cfe84

File tree

2 files changed

+5
-17
lines changed

2 files changed

+5
-17
lines changed

articles/app-service/configure-language-java-apm.md

Lines changed: 4 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -89,11 +89,11 @@ To enable via the Azure CLI, you need to create an Application Insights resource
8989
9090
::: zone-end
9191
92-
::: zone pivot="java-jboss"
92+
<!-- ::: zone pivot="java-jboss"
9393
9494
For **JBoss EAP**, `[TODO]`.
9595
96-
::: zone-end
96+
::: zone-end -->
9797
9898
# [Windows](#tab/windows)
9999
@@ -117,12 +117,6 @@ To enable via the Azure CLI, you need to create an Application Insights resource
117117
118118
::: zone-end
119119
120-
::: zone pivot="java-jboss"
121-
122-
For **JBoss EAP**, `[TODO]`.
123-
124-
::: zone-end
125-
126120
---
127121
128122
> [!NOTE]
@@ -150,11 +144,11 @@ To enable via the Azure CLI, you need to create an Application Insights resource
150144
151145
::: zone-end
152146
153-
::: zone pivot="java-jboss"
147+
<!-- ::: zone pivot="java-jboss"
154148
155149
For **JBoss EAP**, `[TODO]`.
156150
157-
::: zone-end
151+
::: zone-end -->
158152
159153
# [Windows](#tab/windows)
160154
@@ -176,12 +170,6 @@ To enable via the Azure CLI, you need to create an Application Insights resource
176170
177171
::: zone-end
178172
179-
::: zone pivot="java-jboss"
180-
181-
For **JBoss EAP**, `[TODO]`.
182-
183-
::: zone-end
184-
185173
---
186174
187175
## Configure Datadog

articles/app-service/configure-language-java-deploy-run.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -461,7 +461,7 @@ For more information about the CLI commands you can run, see the [Red Hat JBoss
461461

462462
## Clustering
463463

464-
App Service supports clustering for JBoss EAP versions 7.4.1 and greater. To enable clustering, your web app must be [integrated with a virtual network](overview-vnet-integration.md). When the web app is integrated with a virtual network, it restarts, and the JBoss EAP installation automatically starts up with a clustered configuration. When you [run multiple instances with autoscaling](/azure-monitor/autoscale/autoscale-get-started), the JBoss EAP instances communicate over the subnet specified in the virtual network integration, using the ports shown in the `WEBSITES_PRIVATE_PORTS` environment variable at runtime. You can disable clustering by creating an app setting named `WEBSITE_DISABLE_CLUSTERING` with any value.
464+
App Service supports clustering for JBoss EAP versions 7.4.1 and greater. To enable clustering, your web app must be [integrated with a virtual network](overview-vnet-integration.md). When the web app is integrated with a virtual network, it restarts, and the JBoss EAP installation automatically starts up with a clustered configuration. When you [run multiple instances with autoscaling](/azure-monitor/autoscale/autoscale-get-started), the JBoss EAP instances communicate with each other over the subnet specified in the virtual network integration, using the ports shown in the `WEBSITES_PRIVATE_PORTS` environment variable at runtime. You can disable clustering by creating an app setting named `WEBSITE_DISABLE_CLUSTERING` with any value.
465465

466466
:::image type="content" source="media/configure-language-java-deploy-run/jboss-clustering.png" alt-text="A diagram showing a vnet-integrated JBoss App Service app, scaled out to three instances.":::
467467

0 commit comments

Comments
 (0)