Microservices Engine:Java agent versions

Version

The edition type

Release date

Description

4.5.2

Official version

2025-09-11

Throttling protection: Fixed a bug that caused total queries per second (QPS) and total concurrency statistics for the Zuul framework to be doubled.

4.5.0

Not recommended

2025-07-17

• Throttling protection: Added support for the RestTemplate framework.

• Throttling protection: Added support for the Apache HTTP Client (4.x and 5.x) framework.

• Throttling protection: Added support for the OkHttp framework.

• Throttling protection rules: Added a default namespace configuration.

• Removed unexpected rule pulling when the MSE authentication feature is disabled.

• Fixed an issue where the regionId was missing in non-ACK environments if the Alibaba Cloud resource metadata API could not be accessed.

• Fixed a bug where AliyunJavaAgent Nacos incorrectly read the user's AK/SK configuration.

• Fixed a bug where the git.properties file in the AliyunJavaAgent package overwrote user content.

4.4.2

Official version

2025-09-09

• The end-to-end canary release feature is supported by MSE XXL-JOB. You can implement this feature in XXL-JOB without installing a plug-in.

• The coordination between the readiness probe and delayed registration features provided by the graceful start and shutdown solution is optimized in scenarios where an Eureka instance is used as a registry.

• The mechanism to automatically detect Spring MVC versions is optimized for the traffic protection feature.

• The following issue is fixed: The metadata of context-path fails to be collected in specific scenarios when Spring Boot applications are used.

4.3.4

Not recommended

2025-05-12

• The traffic protection architecture is upgraded to ensure compatibility between the agent and open source Sentinel and the overall stability of the microservices governance architecture.

  Note

  For users who have collected MSE metric logs or use open source Sentinel, learn about the changes of MSE agent 4.3.x by referring to Change description on MSE agent 4.3.x.

• Metric classification bugs of the Zuul and Dubbo frameworks are fixed for traffic protection.

• The following issue is fixed: The end-to-end canary release feature does not take effect if Nacos rules are used in the Ribbon framework.

• The following issue is fixed for the end-to-end canary release feature: Traffic is unevenly distributed in round-robin load balancing scenarios when the Feign framework is used.

• XXL-JOB is supported for the end-to-end canary release feature.

• Message filtering on RocketMQ gRPC 5.x clients is supported for the end-to-end canary release for messaging feature.

• The following issue is fixed: Application instances that have the same IP address cannot provide services after you manually de-register an application instance with the IP address.

• The following issue is fixed: If multiple applications are deployed on an Elastic Compute Service (ECS) instance, the status of a manually de-registered application does not meet expectations.

4.2.5

Official edition

2025-04-10

• The following issue is fixed: If the graceful start and shutdown capabilities are enabled, the proactive notification feature does not take effect in specific scenarios.

• The following issue is fixed: The rules for filtering RocketMQ 5 messages based on multiple tags are incorrectly converted when the end-to-end canary release for messaging feature is enabled.

• Server-side message filtering of the RocketMQ Remoting client of a version later than 5.1.0 is supported for the end-to-end canary release for messaging feature.

• Memory performance is stable when throttling rules are frequently triggered for traffic protection.

4.2.2

Official edition

2025-01-09

• End-to-end canary release is supported for RocketMQ 5.0.4 and 5.0.7.

• The following issue is fixed: End-to-end canary release does not work as expected when applications in Dubbo 2.7.x or 3.x are registered with a ZooKeeper registry.

• The concurrency statistics issue that occurs during asynchronous request processing of Spring MVC is fixed for traffic protection.

Version

The edition type

Release date

Description

4.2.0

Not recommended edition

2024-12-06

• Application shutdown events are added for graceful start and shutdown. For more information, see Events.

• The graceful start and shutdown capabilities are supported for Spring Boot 3 applications.

• Event tracking for the Tomcat Servlet framework is supported for traffic protection. By default, this feature is disabled.

• The default circuit-breaking protection mechanism, throttling based on the total queries per second (QPS), throttling based on the total concurrency, and exception settings are added for system protection. For more information, see Configure system protection.

• The logical boundary of Spring Cloud LoadBalancer is optimized for end-to-end canary release.

• The Dubbo 3.x Triple protocol and application-level service discovery are supported for end-to-end canary release.

• The issue that occurred when Spring Cloud applications are registered with a Consul registry is resolved for end-to-end canary release.

• The performance issue of passive notifications is resolved for graceful shutdown.

• The write issue that occurred when the permission on the default log directory is not granted is resolved for Microservices Governance.

4.1.10

Not recommended edition

2024-09-05

• Intra-zone routing priorities are supported for Spring Cloud applications and Dubbo applications.

• By default, the MyBatis plug-in is disabled for MSE traffic protection. You can enable the plug-in by adding an environment variable to the configuration file or applying the startup parameter configuration spring.cloud.ahas.sentinel.mybatis.enabled=true.

• The canary release for messaging is supported for the Ons client.

• The following issue is fixed: The consumer interface in the MSE Dubbo framework is invisible in specific scenarios.

• The bug in the Feign framework for traffic protection is fixed to ensure the normal use of fallback operations in specific scenarios.

4.1.9

Official edition

2024-07-10

• The following issue is fixed: Tag-based routing rules of Dubbo applications fail to be pulled.

• The bug of Microservices Governance in scenarios in which Serverless App Engine (SAE) is used is fixed. The :54199/readiness endpoint is introduced for readiness probe.

• The conflict between the agent and sentinel-spring-webmvc-6x-adapter is fixed.

• Canary release for messaging is supported for RocketMQ 4.x messages that are sent using the synchronization mode or obtained using the pull mode.

• The ALIYUN_JAVA_AGENT_MINIMAL_MEMORY environment variable is used to specify the minimum memory that can run.

• Graceful shutdown is supported for Dubbo 3.2.x and RocketMQ.

3.2.10

Official edition

2024-07-11

The following issue is fixed: Application startup fails in scenarios in which the Spring Cloud Alibaba Sentinel framework is used.

3.2.9

Official edition

2024-03-28

• The custom event tracking feature is supported for traffic protection provided by Microservices Governance. For more information, see Add custom interfaces to Microservices Governance.

• Spring Boot 3.0 to 3.2 are supported in Microservices Governance.

• JDK 21 is supported in Microservices Governance.

• Dubbo 3.x is supported in Microservices Governance.

Version

The edition type

Release date

Description

3.1.4

Official edition

2023-12-25

• The performance issue in the MSE logic is fixed.

• The following issue is fixed: If the value of Related is changed from false to true, the check performed by a readiness probe fails.

• The following issue is fixed: Delayed registration is invalid for Eureka instances.

• In scenarios where only the MSE features are enabled for the agent, ARMS spans, metrics, and metadata are no longer collected.

• The filters of Zuul gateways or Spring Cloud Gateways are used instead of Tomcat to parse request parameters and bodies.

• The fault tolerance logic is added to the end-to-end canary release capability. If the trace is empty, requests are sent to the base environment rather than any other environments.

• Data of the CPU utilization metric of Microservices Governance Enterprise Edition is collected by Sentinel.

3.0.7

Official edition

2023-11-18

• JDK 1.6 and JDK 1.7 are no longer supported in Microservices Governance agent V3.0.7 and later.

• The conflicts between the service authentication switch and other configuration items are fixed.

• The type of the agent thread pool is set to static final to help you obtain the ownership of the thread pool.

• If MSE features are not enabled for the agent, the MSE logic is not executed.

• For the two WebInterceptors that are used for traffic protection, their resource names are aligned with the behavior by default, and the interface names include the context-path prefix.

• The microservices insight feature no longer reports data to the server. The agent stores related data to local logs. You can manually collect the data as needed.

• The following issue is fixed for the traffic protection module: An error is reported when FeignClientBuilder creates a FeignClient in the forType mode.

• Custom remote procedure call (RPC) behavior is supported for traffic protection.

• The SentinelWebInterceptor component can be configured as the starter during the traffic protection process to obtain accurate throttling data.

• The SentinelWebInterceptor component injected by the agent is used as the starter during the traffic protection process when the starter injection mechanism becomes invalid.

2.9.2

Official edition

2023-09-09

• Custom RPC behavior is supported for traffic protection.

• The SentinelWebInterceptor component can be used as the starter during the traffic protection process.

• The SentinelWebInterceptor component injected by the agent is used as the starter during the traffic protection process when the starter injection mechanism becomes invalid.

2.9.1.2

Official edition

2023-08-03

• The following issue is fixed: Traffic loads are not balanced when Spring Cloud Ribbon is used.

• The alicloud_service_tag labels or annotations can be used to tag nodes.

• Microservices Governance is available in the China East 1 Finance region.

• If MSE is not activated, MSE-related logic is not initialized.

• The cache issue of GetLocalV4Ip is fixed.

• The following issue is fixed: Traffic requests fail when Microservices Governance Enterprise Edition uses Spring Cloud Gateway and open source SCA Sentinel at the same time.

• The following issue is fixed: Only the fallback method is supported in the Feign framework for traffic protection.

• The following issue is fixed: The file timestamps of the labels and annotations are inconsistent, which causes frequent re-registration operations.

• The following issue is fixed: Asynchronous trace data is occasionally lost when the Reactor framework is used.

2.9.0

Official edition

2023-07-13

• Traffic protection supports the frameworks of Zuul gateways and Spring Cloud Gateways.

• MSE supports persistent service discovery.

• Canary release and tag-based routing support Dubbo 3.x.

• HTTP body matching is supported for end-to-end canary release rules.

• The performance of graceful start and shutdown in MSE is improved.

2.8.3

Official edition

2023-03-31

• JDK 11 and JDK 17 are supported.

• MSE allows applications in different environments to access different namespaces. This way, applications in different environments such as development environments, test environments, and online environments can be isolated from each other.

• MSE supports traffic protection.

• The microservices insight feature is completely released and the graceful start and shutdown and end-to-end canary release features are improved in terms of observability.

• Microservices Governance provided by MSE supports Consul registries.

• End-to-end canary release supports Consul and Undertow.

Version

The edition type

Release date

Description

2.7.3.5

Official edition

2022-07-27

• Canary release for RocketMQ messages is supported.

• OpenSergo registry tagging and canary release of MSE cloud-native gateways are supported.