You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/java-containers-intro.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: container-apps
5
5
author: craigshoemaker
6
6
ms.service: azure-container-apps
7
7
ms.topic: conceptual
8
-
ms.date: 04/08/2025
8
+
ms.date: 04/09/2025
9
9
ms.author: cshoe
10
10
ai-usage: ai-generated
11
11
---
@@ -43,6 +43,8 @@ Docker is the most popular containerization platform, and is well-supported in t
43
43
44
44
## Set up your development environment
45
45
46
+
This section guides you through installing the necessary tools and configuring your development environment to build, run, and debug containerized Java applications.
47
+
46
48
### Install required tools
47
49
48
50
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
198
200
199
201
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.
200
202
201
-
### Setting Up Remote Debugging
203
+
### Set up remote debugging
202
204
203
205
Debugging containerized Java applications requires exposing a debug port and configuring your IDE to connect to it:
204
206
@@ -231,7 +233,7 @@ Debugging containerized Java applications requires exposing a debug port and con
231
233
232
234
1. Start your container with port `5005` mapped to your host, then launch the debugger in Visual Studio Code.
233
235
234
-
### Troubleshooting Container Issues
236
+
### Troubleshoot container issues
235
237
236
238
When containers don't behave as expected, you can inspect your app's logs to investigate the issue.
237
239
@@ -268,13 +270,13 @@ Common issues include:
268
270
| Permission problems | Verify file system permissions. |
269
271
| Classpath issues | Check JAR structure and dependencies. |
270
272
271
-
## Optimizing Java Containers
273
+
## Optimize Java containers
272
274
273
275
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.
274
276
275
277
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.
276
278
277
-
### JVM Memory Configuration in Containers
279
+
### JVM memory configuration in containers
278
280
279
281
The JVM doesn't automatically detect container memory limits in Java 8. For Java 9+, container awareness is enabled by default.
280
282
@@ -347,11 +349,11 @@ For Spring Boot applications, include the Actuator dependency for comprehensive
347
349
348
350
Configure your application to output logs in a format (like JSON) suitable for container environments.
349
351
350
-
## Deploying to Azure Container Apps
352
+
## Deploy to Azure Container Apps
351
353
352
354
This section guides you through preparing your Java containers for Azure Container Apps deployment and highlights key configuration considerations.
353
355
354
-
### Preparing Your Container for Azure
356
+
### Prepare your container for Azure
355
357
356
358
- **Port configuration**: Ensure your container listens on the port provided by Azure:
0 commit comments