This topic provides answers to frequently asked questions (FAQ) about application monitoring in Application Real-time Management Service (ARMS).
Overview
- FAQ about manually installing the ARMS agent for Java applications
- Is the ARMS agent compatible with the agents of other APM services, such as Pinpoint?
- What can I do if the "OutOfMemoryError" error is reported when I start an application after the ARMS agent is installed?
- How do I test network connectivity?
- How do I check whether the ARMS agent was installed?
- Why is no monitoring data displayed in the ARMS console after I installed the ARMS agent?
- What can I do if no IP address or an invalid IP address is displayed after the ARMS agent was installed?
- How do I troubleshoot errors included in the logs of the ARMS agent that are stored in the ArmsAgent/log directory?
- How do I deploy multiple instances on a single host?
- FAQ about installing the ARMS agent for Java applications with one click
- FAQ about installing the ARMS agent for Java applications deployed on Elastic Compute Service (ECS) instances with one click
- FAQ about installing the ARMS agent for Java applications deployed in Container Service
for Kubernetes (ACK) clusters
- Why is no application monitoring data displayed after the ARMS agent was installed on a Java application of JDK11 in an ACK cluster?
- Why is no application monitoring data displayed after the ARMS agent was installed on a Java application in an ACK cluster?
- What can I do if the ARMS agent cannot be installed for an application in an ACK cluster?
- FAQ about installing the ARMS agent for Java applications deployed in open source Kubernetes environments
- FAQ about modifying the names of Java applications without reinstalling the ARMS agent
- FAQ about uninstalling the ARMS agent
- How do I uninstall the ARMS agent that was installed manually?
- How do I uninstall the ARMS agent that was installed with one click?
- How do I uninstall the ARMS agent that was installed on a Java application deployed on an ECS instance?
- How do I uninstall the ARMS agent that was installed on a Java application deployed in an ACK cluster?
- How do I uninstall the ARMS agent that was installed on a Java application deployed in an open source Kubernetes environment?
- How do I uninstall the ARMS agent that was installed on a Java application deployed in a Docker cluster?
- How do I uninstall the ARMS agent that was installed on a PHP application?
- How do I uninstall the ARMS agent that was installed on a PHP application deployed in an ACK cluster?
- Other FAQ
Is the ARMS agent compatible with the agents of other APM services, such as Pinpoint?
The ARMS agent is incompatible with the agents of other application performance management (APM) services. APM is implemented by using bytecode instrumentation based on the ASM framework. If you install two agents, bytecode instrumentation is performed twice on the code. Agents developed by different vendors use different code to implement bytecode instrumentation. Performance issues may occur due to code conflicts if you install multiple agents. Therefore, we recommend that you do not install the agents of other APM services.
What can I do if the "OutOfMemoryError" error is reported when I start an application after the ARMS agent is installed?
You can add the corresponding heap memory parameters to the start command to increase the memory of the Java virtual machine (JVM). In the following example, the initial size (Xms) of the heap memory is 512 MB and the maximum size (Xmx) of the heap memory is 2 GB.
-Xms512M
-Xmx2048M
If the OutOfMemoryError: PermGen space
error is reported, add the following parameters to the start command:
-XX:PermSize=256M
-XX:MaxPermSize=512M
If the OutOfMemoryError: metaspace
error is reported, add the following parameters to the start command:
-XX:MetaspaceSize=256M
-XX:MaxMetaspaceSize=512M
How do I test network connectivity?
Before you install the ARMS agent, you must make sure that the 8883, 8443, and 8442 ports can be accessed. You can run the Telnet command to check whether the host on which your application is deployed is connected to the ARMS server. For example, to test the connectivity in the China (Shenzhen) region, log on to the host on which the application is deployed and run the following commands:
telnet arms-dc-sz.aliyuncs.com 8883
telnet arms-dc-sz.aliyuncs.com 8443
telnet arms-dc-sz.aliyuncs.com 8442
Region | Endpoint for access from the classic network and the Internet | Endpoint for access from a VPC |
---|---|---|
China (Hangzhou) | arms-dc-hz.aliyuncs.com | arms-dc-hz-internal.aliyuncs.com |
China (Shanghai) | arms-dc-sh.aliyuncs.com | arms-dc-sh-internal.aliyuncs.com |
China (Qingdao) | arms-dc-qd.aliyuncs.com | arms-dc-qd-internal.aliyuncs.com |
China (Beijing) | arms-dc-bj.aliyuncs.com | arms-dc-bj-internal.aliyuncs.com |
China (Zhangjiakou) | arms-dc-zb.aliyuncs.com | arms-dc-zb-internal.aliyuncs.com |
China (Hohhot) | dc-cn-huhehaote.arms.aliyuncs.com | dc-cn-huhehaote-internal.arms.aliyuncs.com |
China (Ulanqab) | dc-cn-wulanchabu.arms.aliyuncs.com | dc-cn-wulanchabu-internal.arms.aliyuncs.com |
China (Shenzhen) | arms-dc-sz.aliyuncs.com | arms-dc-sz-internal.aliyuncs.com |
China (Heyuan) | dc-cn-heyuan.arms.aliyuncs.com | dc-cn-heyuan-internal.arms.aliyuncs.com |
China (Guangzhou) | dc-cn-guangzhou.arms.aliyuncs.com | dc-cn-guangzhou-internal.arms.aliyuncs.com |
China (Chengdu) | dc-cn-chengdu.arms.aliyuncs.com | dc-cn-chengdu-internal.arms.aliyuncs.com |
China (Hong Kong) | arms-dc-hk.aliyuncs.com | arms-dc-hk-internal.aliyuncs.com |
Singapore (Singapore) | arms-dc-sg.aliyuncs.com | arms-dc-sg-internal.aliyuncs.com |
Australia (Sydney) | dc-ap-southeast-2.arms.aliyuncs.com | dc-ap-southeast-2-internal.arms.aliyuncs.com |
Malaysia (Kuala Lumpur) | dc-ap-southeast-3.arms.aliyuncs.com | dc-ap-southeast-3-internal.arms.aliyuncs.com |
Indonesia (Jakarta) | arms-dc-indonesia.aliyuncs.com | arms-dc-indonesia-internal.aliyuncs.com |
Japan (Tokyo) | arms-dc-jp.aliyuncs.com | arms-dc-jp-internal.aliyuncs.com |
Germany (Frankfurt) | arms-dc-frankfurt.aliyuncs.com | arms-dc-frankfurt-internal.aliyuncs.com |
UK (London) | dc-eu-west-1.arms.aliyuncs.com | dc-eu-west-1-internal.arms.aliyuncs.com |
US (Virginia) | dc-us-east-1.arms.aliyuncs.com | dc-us-east-1-internal.arms.aliyuncs.com |
US (Silicon Valley) | arms-dc-usw.aliyuncs.com | dc-us-west-1-internal.arms.aliyuncs.com |
India (Mumbai) | dc-ap-south-1.arms.aliyuncs.com | dc-ap-south-1-internal.arms.aliyuncs.com |
China North 2 Ali Gov 1 | arms-dc-gov.aliyuncs.com | arms-dc-gov-internal.aliyuncs.com |
China East 1 Finance | arms-dc-hz-finance.aliyuncs.com | arms-dc-hz-finance-internal.aliyuncs.com |
China East 2 Finance | arms-dc-sh-finance.aliyuncs.com | arms-dc-sh-finance-internal.aliyuncs.com |
China South 1 Finance | arms-dc-sz-finance.aliyuncs.com | arms-dc-sz-finance-internal.aliyuncs.com |
How do I check whether the ARMS agent was installed?
You can run the following ps command to check whether the ARMS agent was installed successfully when the start command was run.
ps -ef grep 'arms-bootstrap'
The results shown in the following figure indicate that the ARMS agent was installed successfully.

The value of the Darms.licenseKey parameter in the command must be the same as the license key displayed on the Add Application page in the ARMS console.

Why is no monitoring data displayed in the ARMS console after I installed the ARMS agent?
- If the log of the ARMS agent contains
send agent metrics. no metrics.
, check whether your application is continuously accessed by external requests and whether the development framework is supported by the ARMS agent. The external requests include HTTP requests, High-Speed Service Framework (HSF) requests, and Dubbo requests. For more information about third-party components and frameworks supported by the ARMS agent, see Overview. - Check whether the specified time range for query is valid. Set the query time range to the last 15 minutes and check whether monitoring data is displayed.
- If you start the ARMS agent by running the
-jar
command, check the setting of the command and make sure that the -javaagent parameter is before-jar
. The following command provides an example on how to add parameters to the start command:java -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey=xxx -Darms.appName=xxx -jar demoApp.jar
- If the logs stored in ArmsAgent/log/ include the "LicenseKey is invalid." error, check whether the region to which the application belongs is consistent with the region to which the agent belongs.
- After your application is started, if the log folder does not exist in the ArmsAgent folder, the arms-bootstrap-1.7.0-SNAPSHOT.jar package fails to be loaded. Check whether the permissions on the ArmsAgent folder are obtained.
-
If the following error is reported when your application is started, check whether the arms-bootstrap-1.7.0-SNAPSHOT.jar package and the corresponding permissions are correct.
Error opening zip file or JAR manifest missing: /root/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar Error occurred during initialization of VM agent library failed to init: instrument
- If no monitoring data is displayed, compress the logs of the ARMS agent for Java applications
in the ArmsAgent/log directory into a compressed file, and contact the DingTalk account
arms160804
for support. -
Check the Java Development Kit (JDK) version. If the JDK version is 1.8.0_25 or 1.8.0_31, you may fail to install the agent. We recommend that you update the JDK or contact the DingTalk account
arms160804
.
What can I do if no IP address or an invalid IP address is displayed after the ARMS agent was installed?
- You can run the ifconfig -a command to check the network configuration of the current host. If the host uses multiple network interface controllers (NICs), the IP address obtained by the ARMS agent may be inconsistent with the actual IP address due to network configurations.
- You can solve the problem by using one of the following methods:
- Configure the
-DEAGLEEYE.LOCAL.IP=10.XX.XX.XX
parameter of the JVM.Note Replace10.XX.XX.XX
with the actual IP address. - Configure the ARMS agent to obtain the value of the
-DNETWORK.INTERFACE=eth0
parameter, in whicheth0
indicates the NIC name.
- Configure the
How do I troubleshoot errors included in the logs of the ARMS agent that are stored in the ArmsAgent/log directory?
If the "LicenseKey is invalid" error is included in the logs, perform the following operations to troubleshoot the error:
- Make sure that the application is created in ARMS and the license key that you specified when the ARMS agent is installed is valid.
- ARMS supports multiple regions. Therefore, check whether the download URL of the ARMS agent is in the same region as your application.
How do I deploy multiple instances on a single host?
To deploy multiple instances of an application on a single host, set the -Darms.agentId parameter to specify the JVM process to connect to. This parameter indicates a logical number such as 001 and 002. The following command provides an example on how to deploy multiple instances on a single host:
java -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey=<LicenseKey> -Darms.appName=<AppName> -Darms.agentId=001 -jar demoApp.jar
What can I do if getcwd errors are reported when I run the script to access a Java application?
The following error message may be returned after you run the script to access the Java application with one click:
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory Error occurred during initialization of VM java.lang.Error: Properties init: Could not determine current working directory. at java.lang.System.initProperties(Native Method) at java.lang.System.initializeSystemClass(System.java:1119)
This may be because the current directory is accidentally deleted when the script
is running. To solve this problem, run the cd
command and then run the script again.
Where can I view logs after I install the ARMS agent with one click?
By default, the logs are stored in the/root/.arms/supervisor/logs/ directory. If no logs are stored in this directory, run the ps -ef grep arms
command to view the directory where the logs are stored.
What do I do if the ARMS agent cannot be installed?
- Make sure that your ECS instance can access the download URL of the ARMS agent over
the Internet in the region in which the ECS instance is located.
Region Download URL over the Internet China (Hangzhou) arms-apm-cn-hangzhou.oss-cn-hangzhou.aliyuncs.com/ArmsAgent.zip China (Shanghai) arms-apm-cn-shanghai.oss-cn-shanghai.aliyuncs.com/ArmsAgent.zip China (Qingdao) arms-apm-cn-qingdao.oss-cn-qingdao.aliyuncs.com/ArmsAgent.zip China (Beijing) arms-apm-cn-beijing.oss-cn-beijing.aliyuncs.com/ArmsAgent.zip China (Zhangjiakou) arms-apm-cn-zhangjiakou.oss-cn-zhangjiakou.aliyuncs.com/ArmsAgent.zip China (Hohhot) arms-apm-cn-huhehaote.oss-cn-huhehaote.aliyuncs.com/ArmsAgent.zip China (Ulanqab) arms-apm-cn-wulanchabu.oss-cn-wulanchabu.aliyuncs.com/ArmsAgent.zip China (Shenzhen) arms-apm-cn-shenzhen.oss-cn-shenzhen.aliyuncs.com/ArmsAgent.zip China (Heyuan) arms-apm-cn-heyuan.oss-cn-heyuan.aliyuncs.com/ArmsAgent.zip China (Guangzhou) arms-apm-cn-guangzhou.oss-cn-guangzhou.aliyuncs.com/ArmsAgent.zip China (Chengdu) arms-apm-cn-chengdu.oss-cn-chengdu.aliyuncs.com/ArmsAgent.zip China (Hong Kong) arms-apm-cn-hongkong.oss-cn-hongkong.aliyuncs.com/ArmsAgent.zip Singapore (Singapore) arms-apm-ap-southeast-1.oss-ap-southeast-1.aliyuncs.com/ArmsAgent.zip Australia (Sydney) arms-apm-ap-southeast-2.oss-ap-southeast-2.aliyuncs.com/ArmsAgent.zip Malaysia (Kuala Lumpur) arms-apm-ap-southeast-3.oss-ap-southeast-3.aliyuncs.com/ArmsAgent.zip Indonesia (Jakarta) arms-apm-ap-southeast-5.oss-ap-southeast-5.aliyuncs.com/ArmsAgent.zip Japan (Tokyo) arms-apm-ap-northeast-1.oss-ap-northeast-1.aliyuncs.com/ArmsAgent.zip Germany (Frankfurt) arms-apm-eu-central-1.oss-eu-central-1.aliyuncs.com/ArmsAgent.zip UK (London) arms-apm-eu-west-1.oss-eu-west-1.aliyuncs.com/ArmsAgent.zip US (Virginia) arms-apm-us-east-1.oss-us-east-1.aliyuncs.com/ArmsAgent.zip US (Silicon Valley) arms-apm-us-west-1.oss-us-west-1.aliyuncs.com/ArmsAgent.zip India (Mumbai) arms-apm-ap-south-1.oss-ap-south-1.aliyuncs.com/ArmsAgent.zip China North 2 Ali Gov 1 arms-apm-cn-north-2-gov-1.oss-cn-north-2-gov-1.aliyuncs.com/ArmsAgent.zip - Make sure that your ECS instance can access the ARMS console.
- Log on to the ECS console and perform the following operations:
- In the left-side navigation pane, choose .
- On the Cloud Assistant page, click the Commands tab, click the search box and select Command Name, enter
InstallJavaAgent
, and then press the Enter key.Note If no result is returned for the search, contact the DingTalk accountarms160804
for support. - On the Cloud Assistant page, click the Command Execution Result tab and enter the task ID of the
InstallJavaAgent
command in the search box. In the search results, click View in the Actions column of this command and check whether this command is run. If the command fails to run, troubleshoot the errors based on the execution results. For example, if this issue is caused because the disk of the ECS instance is full or the ARMS agent is not installed, clear the disk or install the ARMS agent. If this issue cannot be resolved, send the execution results to the DingTalk accountarms160804
for support.
What can I do if the information about the processes of the ECS instance is inaccurate after the ARMS agent was installed?
If the information about the processes of the ECS instance is not displayed or is
inaccurate after the ARMS agent was installed, click the - icon on the left side of the ECS instance and click the + icon to refresh the data. If the issue cannot be resolved, contact the DingTalk account
arms160804
for support.
What can I do if I cannot enable ARMS application monitoring for a process on an ECS instance?
Check whether the /root/.arms/supervisor/logs/arms-supervisor.log
file of the ECS instance has errors. If the log file has errors, troubleshoot the
error based on the error message. If the error cannot be resolved, contact the DingTalk
account arms160804
for support.
Why is no application monitoring data displayed after the ARMS agent was installed on a Java application of JDK11 in an ACK cluster?
Possible cause: the JDK version parameter is not contained in the YAML file of the application.
Solution: Perform the following steps to add the JDK version parameter to the YAML file of the application.
Why is no application monitoring data displayed after the ARMS agent was installed on a Java application in an ACK cluster?
What can I do if the ARMS agent cannot be installed for an application in an ACK cluster?
Solution: Grant ACK the permissions to access ARMS.
Why is no application monitoring data displayed after the ARMS agent was installed on a Java application of JDK11 in an open source Kubernetes cluster?
Possible cause: the JDK version parameter is not contained in the YAML file of the application.
Solution: In the YAML file, go to the spec -> template -> metadata -> labels section and append the following content:
one-agent.jdk.version: "OpenJDK11"
What can I do if an application cannot be started?
Run the following command to view ack-onepilot logs and troubleshoot the error based on the logs:
k logs -f ack-onepilot-ack-onepilot-XXXX-XXXX -n ack-onepilot
k get pod -n ack-onepilot
command.
How do I view the logs of the ARMS agent?
On the worker of the ACK cluster, view the /home/admin/.opt/ArmsAgent/logs/xxxx.log file.
How do I modify the name of a common Java application on which the ARMS agent was manually installed?
Common Java applications refer to the Java applications that are not deployed on ECS instances. If you manually install the ARMS agent on the application, the directory of the agent is specified by you during the installation.
You can check the version of the ARMS agent by viewing the version file in the directory
of the agent. For example, 2.5.8_cf020486_20190816150025
indicates that the version of the ARMS agent is 2.5.8 and was released on August
16, 2019.
- If the version of the ARMS agent is earlier than 2.5.8.1, uninstall the agent and
install it again. You can specify a new application name when you reinstall the agent.
- For more information about how to uninstall the ARMS agent that was installed manually, see How do I uninstall the ARMS agent that was installed manually?
- For more information about how to uninstall the ARMS agent that was installed with one click, see How do I uninstall the ARMS agent that was installed with one click?
- For more information about how to uninstall the ARMS agent that was installed on a Java application deployed on an ECS instance, see How do I uninstall the ARMS agent that was installed on a Java application deployed on an ECS instance?
- If the version of the ARMS agent is 2.5.8.1 or later, you can perform the following
steps to modify the name of the Java application without reinstalling the ARMS agent.
Note ARMS agents downloaded after August 20, 2019 support this feature.
If the standard output shown in the following figure is displayed, it indicates that the application name is modified.

How do I modify the name of a common Java application on which the ARMS agent was installed with one click?
If you install the ARMS agent with one click, the agent is installed in the ~/.arms/supervisor/agent directory. You must use the same account as the application.
Perform the following steps to modify your application name:
How do I modify the name of a Java application deployed on an ECS instance?
If your Java application is deployed on an ECS instance, the ARMS agent directory is /.arms/agent.
Perform the following steps to modify your application name:
If the standard output shown in the following figure is displayed, it indicates that the application name is modified.

How do I modify the name of a Java application deployed in an ACK cluster?
You can check the version of the ARMS agent by viewing the version file in the directory
of the agent. For example, 2.5.8_cf020486_20190816150025
indicates that the version of the ARMS agent is 2.5.8 and was released on August
16, 2019.
- If the version of the ARMS agent is earlier than 2.5.8.1, uninstall the agent and
install it again. You can specify a new application name when you reinstall the agent.
- For more information about how to uninstall the ARMS agent that was installed manually, see How do I uninstall the ARMS agent that was installed manually?
- For more information about how to uninstall the ARMS agent that was installed with one click, see How do I uninstall the ARMS agent that was installed with one click?
- For more information about how to uninstall the ARMS agent that was installed on a Java application deployed on an ECS instance, see How do I uninstall the ARMS agent that was installed on a Java application deployed on an ECS instance?
- If the version of the ARMS agent is 2.5.8.1 or later, you can perform the following
steps to modify the name of the Java application without reinstalling the ARMS agent.
Note ARMS agents downloaded after August 20, 2019 support this feature.
Change the value of the armsPilotCreateAppName parameter in the Deployment and restart the pod.
Wait a moment after your application name is modified. Monitoring data of the application is reported by using the new name rather than the previous name.
How do I modify the name of a Java application deployed in EDAS?
The names of Java applications deployed in Enterprise Distributed Application Service (EDAS) cannot be modified.
How do I uninstall the ARMS agent that was installed manually?
For more information about how to manually install the ARMS agent on Java applications, see Manually install the ARMS agent for a Java application. You can perform the following steps to uninstall the ARMS agent that was installed manually:
- If you no longer want to use ARMS to monitor your Java applications, delete all parameters related to AppName and LicenseKey, which are described in Step 8.
- Restart the Java application.
How do I uninstall the ARMS agent that was installed with one click?
For more information about how to install the ARMS agent with one click, see Install the ARMS agent for a Java application by using scripts. You can perform the following steps to uninstall the ARMS agent that was installed with one click:
How do I uninstall the ARMS agent that was installed on a Java application deployed on an ECS instance?
How do I uninstall the ARMS agent that was installed on a Java application deployed in an ACK cluster?
If you no longer want to use ARMS to monitor a Java application deployed in an ACK cluster, perform the following steps to uninstall the ARMS agent:
- Log on to the Alibaba Cloud Container Service for Kubernetes console .
- In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that contains the Java application from which you want to uninstall the ARMS agent and click Applications in the Actions column.
- In the left-side navigation pane, choose .
- On the Helm page, find the release named arms-pilot of the ARMS agent, and click Delete in the Actions column.
- In the Delete message, click OK.
- Restart your business pod.
How do I uninstall the ARMS agent that was installed on a Java application deployed in an open source Kubernetes environment?
How do I uninstall the ARMS agent that was installed on a Java application deployed in a Docker cluster?
- If you no longer want to use ARMS to monitor a Java application deployed in a Docker cluster, delete the content of the Dockerfile edited in Step 1 in the Install the ARMS agent for a Java application deployed in a Docker cluster topic.
- Run the docker build command to build an image.
- Run the docker run command to start the image.
How do I uninstall the ARMS agent that was installed on a PHP application?
If you no longer want to use ARMS to monitor a PHP application that is not deployed in an ACK cluster, perform the following steps to uninstall the ARMS agent:
How do I uninstall the ARMS agent that was installed on a PHP application deployed in an ACK cluster?
If you no longer want to use ARMS to monitor a PHP application deployed in an ACK cluster, perform the following steps to uninstall the ARMS agent:
- Log on to the Alibaba Cloud Container Service for Kubernetes console .
- In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that contains the Java application from which you want to uninstall the ARMS agent and click Applications in the Actions column.
- In the left-side navigation pane, choose .
- On the Helm page, find the release named arms-pilot of the ARMS agent, and click Delete in the Actions column.
- In the Delete message, click OK.
- Restart your business pod.
What can I do if the data of my application that uses the OpenFeign component is incomplete in ARMS?
After your application that uses the OpenFeign component is connected to ARMS application monitoring, the application data may be incomplete and the data of downstream applications may fail to be viewed. This may be because the OpenFeign component enables Hystrix that uses the RxJava asynchronous framework by default. However, ARMS does not support asynchronous frameworks.
You can disable Hystrix and enable the OkHttp request class to resolve this issue.
- Add the following dependency to the pom.xml file:
<!-- OKHttp supports Feign --> <dependency> <groupId>io.github.openfeign</groupId> <artifactId>feign-okhttp</artifactId> </dependency>
- Add the following content to the SpringCloud configuration file:
feign.okhttp.enabled: true feign.hystrix.enabled: false
- Configure the OkHttp request class.
@Configuration @ConditionalOnClass(Feign.class) @AutoConfigureBefore(FeignAutoConfiguration.class) public class FeignClientOkHttpConfiguration { @Bean public OkHttpClient okHttpClient() { return new OkHttpClient.Builder() // The connection times out. .connectTimeout(20, TimeUnit.SECONDS) // The response times out. .readTimeout(20, TimeUnit.SECONDS) // The write request times out. .writeTimeout(20, TimeUnit.SECONDS) // Indicates whether to enable automatic reconnection. .retryOnConnectionFailure(true) // The connection pool. .connectionPool(new ConnectionPool()) .build(); }