Help Center/ Application Performance Management/ Service Overview（2.0）/ JavaAgent Updates
Updated on 2025-11-19 GMT+08:00
View PDF
Share

JavaAgent Updates

Constraints

  • Only JDK 8, JDK 11, JDK 17, and JDK 21 are supported.
  • In the JDK 8 environment, select a version not ended with -jdkxx. In other JDK environments, select a version ended with -jdkxx. If profiling is required, select a version ended with -profiler.
  • To download Agents, see Agent Download Addresses.
  • For versions ended with -jdk17, add -jdk17 to the end of the Agent download path.

    Example: If the download address for Agent 2.4.8 is https://apm2-javaagent***/apm2_javaagent/apm-javaagent-2.4.8.tar, that address for Agent 2.4.8-jdk17 will be https://apm2-javaagent***/apm2_javaagent/apm-javaagent-2.4.8-jdk17.tar.

Table 1 JavaAgent updates

Version

Description

2.5.5
  1. Optimized the metric and trace reporting performance.

2.5.4
  1. Supported the display of springboot3.x path parameters for API calling.
  2. Fixed the issue that the debugger on the client does not work when the server restarts.

2.5.3
  1. Added the tag lubanops-nenv-id to the root span of the node, which indicates the environment ID registered by the upstream service on the APM server.

2.5.2
  1. The Java method configuration logic is optimized and can take effect automatically.

2.5.1
  1. JavaAgent versions (including different Profiler and JDK versions) are integrated.

2.4.14

2.4.14-jdk17
  1. Supported trace generation based on the OpenTelemetry protocol.
  2. Fixed the issue that the gateway service returns multiple trace IDs.
  3. Fixed the issue that HttpClient collection is incomplete.
  4. Fixed the issue that the regular expression for external calls is invalid.

2.4.13

2.4.13-jdk17
  1. (SQL collector) Supported the setting and collection of slow SQL queries and database names.
  2. (URL collector) Supported exception counting by URL and exception type.

2.4.12

2.4.12-jdk17

2.4.12-jdk21
  1. Optimized concurrency increase logic.

2.4.11

2.4.11-jdk17

2.4.11-jdk11
  1. 2.4.11-jdk11 supports JDK 11. This function is available only for certain users in the CN East-Shanghai1 region.

2.4.10

2.4.10-jdk17
  1. Thread details are reported based on quantity.
  2. The SpringBean function supports the @service annotation.

2.4.9
  1. Shortened Spring Bean boot time.

2.4.7
  1. Enabled you to configure the number of SQL bytes to collect.
  2. Supported the Spring Bean plug-in.
  3. Supported Jedis 2.9.3.

2.4.5-jdk17
  1. Supported HttpClient 5 only in the synchronization scenario.

2.4.5
  1. Supported the aging mechanism for metric collection queues.

2.4.4
  1. Supported Spring Cloud Gateway (2.1.x to 3.1.x).

2.4.3
  1. Fixed the problem that the number of exceptions is not reset.
  2. Fixed the problem that logs are too large.
  3. Added basic Redisson information.

2.4.2-jdk17
  1. Supported JDK 17 only.

2.4.2
  1. Allowed the Agent to be disabled during FunctionGraph startup.

2.4.1
  1. Supported dynamic settings for the metric collection threshold.
  2. Displayed Exceptions in the URL summary. It is the number of exceptions marked in URL logs.
  3. Supported data transmission through a proxy.

2.3.19
  1. Printed trace IDs in logs.
  2. Provided more thread details.

2.3.17
  1. Read an AK/SK from environment variables.
  2. Added SQL IDs to traces.
  3. Added the latest trace for SQL.
  4. Added cluster-based analysis for URLs.

2.3.16
  1. Supported registration with a specified protocol.
  2. Compatible with the IBM SDK that does not return the thread memory.

2.3.15
  1. Supported Dubbo 2.8.x.
  2. Supported JDK HTTP subclasses.

2.3.13
  1. Supported multi-key BizCode for CSE Provider.
  2. Supported the Hikari plug-in.

2.3.12
  1. Continued to collect keys even though the number of HashMap keys exceeds the threshold.
  2. Supported automatic URL normalization. After this function is enabled in the backend, URLs are normalized based on the original format.
  3. Supported the collection of rows read and updated for the Oracle plug-in.
  4. Supported the display of BizCode for CSE Provider.
  5. (CSE Provider) Marked the trace in red when status code 400 is returned.

2.3.5
  1. Supported configuration of an access address in the startup script.

2.3.2
  1. Supported Jetty-client.
  2. Canceled the support for com.huawei.bsp.commonlib.roa.restclient.
  3. Supported collection of Apdex values for the URL collector.

2.3.1
  1. Supported SK decryption on CCE.
  2. Supported key and value interception for the Jedis collector.
  3. Support Cassandra3.

2.2.15
  1. Supported custom SK decryption.
  2. Supported configuration of a master address in the startup script.
  3. Supported collection of response bodies for the apacheHttpclient collector.

2.2.13
  1. Returned original bytecode when NamedTransformer is used to load interface classes.
  2. Solved the problem that MariaDB 3.0.4 SQL data cannot be collected.
  3. Supported Oracle.

2.2.10
  1. Supported the gauss-zenith database.
  2. Supported com.huawei.bsp.commonlib.roa.restclient.

2.2.9
  1. Supported jetcd 5.x–6.x.
  2. Supported collection of Netty direct memory.
Table 2 Latest JavaAgent versions on CCE and ServiceStage

Version

Actual Version

latest-x86_64
  1. 2.4.3; supporting x86 architecture

latest-aarch64
  1. 2.4.3; supporting the Arm architecture

latest-noroot-x86_64
  1. 2.4.3; supporting the x86 architecture and allowing non-root users to run containers

latest-noroot-aarch64
  1. 2.4.3; supporting the Arm architecture and allowing non-root users to run containers

latest
  1. 2.1.17; compatible with x86 and Arm architectures