When you deploy a WAR or JAR application on a Container Service Kubernetes cluster or ACK Serverless cluster, Enterprise Distributed Application Service (EDAS) provides built-in Tomcat settings. Configure the application port, context path, thread pool size, and character encoding to match your runtime requirements -- either during application creation or when updating an existing deployment.
Tomcat parameters
The following table describes the parameters available in the Tomcat Configuration panel.
| Parameter | Description | Default |
|---|---|---|
| Application Port | The port that Tomcat listens on. Valid range: 1024--65535. Ports below 1024 require root permissions, which the container does not grant. | 8080 |
| Tomcat Context | The context path for your application. Three options: Package Name (uses the JAR or WAR file name), Root Directory (sets the path to /), or Custom (specify a value in the Custom Path field). | -- |
| Maximum Threads | The maximum number of request-processing threads. Maps to the Tomcat maxThreads attribute in server.xml. | 400 |
| Tomcat Encoding | The character encoding for URI parameters. Valid values: UTF-8, ISO-8859-1, GBK, GB2312. | ISO-8859-1 |
| Use Advanced Settings | Edit the server.xml file directly. Available only for WAR package deployments. | -- |
Maximum Threads directly affects application performance and stability. Set this value based on load testing results rather than arbitrary estimates.
Set Tomcat parameters for a new application
Log on to the EDAS console.
In the left-side navigation pane, choose Application Management > Applications.
In the top navigation bar, select a region. In the upper part of the page, select a namespace.
In the upper-left corner, click Create Application.
In the Basic Information step, configure the following parameters and click Next.
NoteIf you select Custom as the runtime environment, Tomcat Configuration does not appear on the Advanced Settings tab. The Custom option uses the Tomcat configuration bundled with your application image.
Parameter Action Cluster Type Select Kubernetes Clusters. Application Runtime Environment Select one of the following: Java (JAR package, Dubbo or Spring Boot), Tomcat (WAR package, Dubbo or Spring), or EDAS-Container (HSF) (WAR or FatJar, High-speed Service Framework with Ali-Tomcat and Pandora). In the Configurations step, set the environment, basic information, deployment method, and resource parameters, and then click Next.
In the Advanced Settings step, click Tomcat Configuration, select Custom Configuration, and then click Edit.
In the Application Settings dialog box, set the parameters described in Tomcat parameters and click OK.
Click Create Application.
On the Creation Completed page, review the settings in Basic Information, Configurations, and Advanced Settings, and then click Create Application.
Update Tomcat parameters for an existing application
Updating the Tomcat configuration restarts the application. Perform this operation during off-peak hours.
Log on to the EDAS console.
In the left-side navigation pane, choose Application Management > Applications.
In the top navigation bar, select a region. In the upper part of the page, select a namespace.
From the Cluster Type drop-down list, select Container Service or Serverless Kubernetes Cluster.
Find the target application and click its name.
On the Overview or Basic information page, choose Deploy > Deploy in the upper-right corner.
On the Select Deployment Mode page, select a deployment mode and click Start Deployment.
Set the application environment and deployment package information. In the Advanced Settings step, click Tomcat Configuration, select Custom Configuration, and then click Edit.
In the Edit Tomcat Configuration dialog box, set the parameters described in Tomcat parameters and click OK.
Verify the configuration
After deployment completes, verify that the Tomcat configuration is active:
Check the change list: In the left-side navigation pane of the application details page, click Change List. If the Change Status column shows Succeeded, the configuration is in effect.
Check pod status: On the Application Overview page, click Running Pods (Click View) next to Running Status. In the Pod section, check the Status column. A green dot indicates the application is running with the updated configuration.