DynamicTp: A SpringBoot‑Based Dynamic Thread‑Pool Framework for Java Applications

DynamicTp is a SpringBoot starter that extends the standard ThreadPoolExecutor to provide dynamic runtime configuration, real‑time monitoring, and alerting capabilities for Java thread pools.

Background

Thread pools are widely used in Java projects to improve performance, but configuring core parameters is often uncertain, requires manual restarts, and lacks visibility during operation.

DynamicTp leverages configuration centers (e.g., Nacos, Apollo, Zookeeper, Consul, Etcd) to adjust thread‑pool parameters on the fly, reducing development effort and improving high‑availability.

Features (v1.0.9)

Zero‑intrusion code : All settings are externalized in the configuration center.

Lightweight : Implemented as a SpringBoot starter , integration takes only four steps.

Highly extensible : Core functions expose SPI interfaces for custom implementations (configuration parsing, notification, monitoring, task wrapping, etc.).

Large‑scale production : Proven in Meituan’s internal thread‑pool practice.

Multi‑platform alerts : Supports DingTalk, WeChat Work, Feishu, email, and custom SPI extensions.

Monitoring : Provides metrics via MicroMeter , JsonLog , and Endpoint .

Task enhancement : Offers task wrappers such as TaskWrapper , MdcTaskWrapper , TtlTaskWrapper , and SwTraceTaskWrapper for context propagation.

Compatibility : Works with JUC thread pools and Spring’s ThreadPoolTaskExecutor using the @DynamicTp annotation.

Multi‑mode executors : Includes an IO‑intensive EagerDtpExecutor similar to Tomcat’s pool.

Support for multiple configuration centers : Nacos, Apollo, Zookeeper, Consul, Etcd, etc.

Middleware thread‑pool management : Integrated management for Tomcat, Jetty, Undertow, Dubbo, RocketMQ, Hystrix, Grpc, and more.

Architecture Design

The framework consists of the following modules:

Configuration change listening module

Internal service thread‑pool management module

Third‑party component thread‑pool management module

Monitoring module

Notification & alarm module

Module Details

Configuration Change Listening

1. Listens to configuration files in supported centers (Nacos, Apollo, Zookeeper, Consul, Etcd) via SPI extensions. 2. Parses yml , properties , and json files. 3. Notifies the thread‑pool management module to refresh parameters.

Internal Service Thread‑Pool Management

1. On service startup, pulls configuration from the center, creates ThreadPoolExecutor instances, and registers them in an internal registry and Spring context. 2. Responds to refresh events to update parameters at runtime. 3. Instances can be obtained via dependency injection or DtpRegistry.getDtpExecutor() by name.

Third‑Party Component Management

Manages thread pools of common middleware (Tomcat, Jetty, Undertow, Dubbo, RocketMQ, Hystrix, Grpc) and handles parameter refresh, metric collection, and alerting.

Monitoring Module

Provides three default metric output methods:

JsonLog – writes metrics to disk for custom parsing.

MicroMeter – integrates with Micrometer and Grafana dashboards.

Endpoint – exposes an HTTP endpoint ( dynamic-tp ) for real‑time metric access.

Notification & Alarm Module

Supports alerts for parameter changes, queue capacity thresholds, pool activity thresholds, rejection policies, task execution timeouts, and task waiting timeouts. Integrated with DingTalk, WeChat Work, Feishu, and email, with SPI for custom channels.

Open‑Source Repository

https://github.com/dromara/dynamic-tp