Skip to content

Commit 6d89554

Browse files
updates
1 parent 4bc07c9 commit 6d89554

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

articles/container-apps/java-containers-intro.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.topic: conceptual
8-
ms.date: 04/08/2025
8+
ms.date: 04/09/2025
99
ms.author: cshoe
1010
ai-usage: ai-generated
1111
---
@@ -43,6 +43,8 @@ Docker is the most popular containerization platform, and is well-supported in t
4343

4444
## Set up your development environment
4545

46+
This section guides you through installing the necessary tools and configuring your development environment to build, run, and debug containerized Java applications.
47+
4648
### Install required tools
4749

4850
To containerize Java applications, you need several tools installed on your development machine:
@@ -198,7 +200,7 @@ Debugging containerized Java applications is sometimes challenging because your
198200
199201
Standard debugging approaches don't always directly apply, but with the right configuration, you can establish a remote debugging connection to your application. This section shows you how to configure your containers for debugging, connect your development tools to running containers, and troubleshoot common container-related issues.
200202
201-
### Setting Up Remote Debugging
203+
### Set up remote debugging
202204
203205
Debugging containerized Java applications requires exposing a debug port and configuring your IDE to connect to it:
204206
@@ -231,7 +233,7 @@ Debugging containerized Java applications requires exposing a debug port and con
231233

232234
1. Start your container with port `5005` mapped to your host, then launch the debugger in Visual Studio Code.
233235

234-
### Troubleshooting Container Issues
236+
### Troubleshoot container issues
235237

236238
When containers don't behave as expected, you can inspect your app's logs to investigate the issue.
237239

@@ -268,13 +270,13 @@ Common issues include:
268270
| Permission problems | Verify file system permissions. |
269271
| Classpath issues | Check JAR structure and dependencies. |
270272

271-
## Optimizing Java Containers
273+
## Optimize Java containers
272274

273275
Java applications in containers require special consideration for optimal performance. The JVM was designed before containers were common, which can lead to resource allocation issues if not properly configured.
274276

275277
By fine-tuning memory settings, optimizing image size, and configuring garbage collection, you can significantly improve the performance and efficiency of your containerized Java applications. This section covers essential optimizations for Java containers with a focus on memory management, startup time, and resource utilization.
276278

277-
### JVM Memory Configuration in Containers
279+
### JVM memory configuration in containers
278280

279281
The JVM doesn't automatically detect container memory limits in Java 8. For Java 9+, container awareness is enabled by default.
280282

@@ -347,11 +349,11 @@ For Spring Boot applications, include the Actuator dependency for comprehensive
347349

348350
Configure your application to output logs in a format (like JSON) suitable for container environments.
349351

350-
## Deploying to Azure Container Apps
352+
## Deploy to Azure Container Apps
351353

352354
This section guides you through preparing your Java containers for Azure Container Apps deployment and highlights key configuration considerations.
353355

354-
### Preparing Your Container for Azure
356+
### Prepare your container for Azure
355357

356358
- **Port configuration**: Ensure your container listens on the port provided by Azure:
357359

0 commit comments

Comments
 (0)