Dynamic ThreadPool (DynamicTp) – Runtime Adjustable Thread Pool Framework Overview

Background

Many Java projects rely on thread pools for performance, yet developers often struggle with choosing core parameters, adjusting them after deployment, and lacking visibility into pool behavior.

1. Uncertainty about optimal core parameters for ThreadPoolExecutor. 2. Parameter changes require code redeployment. 3. Thread pools act as a black box without real‑time insight.

DynamicTp addresses these pain points by enabling dynamic, runtime configuration of thread‑pool parameters through a configuration center, providing zero‑intrusion, lightweight integration with SpringBoot, and high availability.

Introduction

DynamicTp enhances ThreadPoolExecutor with three main goals: dynamic parameter modification at runtime, real‑time monitoring with alerting, and periodic metric collection for dashboards like Grafana.

Version v1.0.9 introduces features such as zero‑intrusion configuration, simple starter‑based integration, SPI‑based extensibility, large‑scale production use (e.g., Meituan), multi‑platform alerting (WeChat Work, DingTalk, Feishu, email), various monitoring outputs (MicroMeter, JsonLog, Endpoint), task wrappers for context propagation, compatibility with JUC pools and Spring's ThreadPoolTaskExecutor, graceful shutdown handling, and support for multiple configuration centers (Nacos, Apollo, Zookeeper, Consul, Etcd).

Architecture Design

The framework consists of several modules:

1. Configuration change listener module 2. Internal service thread‑pool management module 3. Third‑party component thread‑pool management module 4. Monitoring module 5. Notification & alert module

Code Structure

Modules include:

adapter – adapts third‑party component pools (Tomcat, Jetty, Undertow, Dubbo, RocketMQ, Hystrix, gRPC).

common – shared utilities.

core – core logic for dynamic adjustment, monitoring, and alerting.

example – usage examples.

extension – optional extensions (Redis flow control, email, SkyWalking context).

logging – logging of monitoring data.

starter – auto‑configuration and dependency packaging.

Configuration Change Listener Module

Listens to configuration files in supported centers (Nacos, Apollo, Zookeeper, Consul, Etcd), parses yml/properties/json, and notifies the thread‑pool management module to refresh parameters.

Internal Service Thread‑Pool Management Module

Creates pool instances at startup from configuration, registers them, and updates them upon refresh events; pools can be accessed via dependency injection or DtpRegistry.getDtpExecutor().

Third‑Party Component Thread‑Pool Management

Manages pools of external middleware, handling parameter refresh, metric collection, and alerting.

Monitoring Module

Provides metric collection with three default outputs: JsonLog to disk, MicroMeter for Prometheus/Grafana, and a custom HTTP endpoint (dynamic‑tp).

Notification & Alert Module

Integrates with office platforms (DingTalk, WeChat Work, Feishu, email) to send alerts for parameter changes, queue capacity thresholds, pool activity thresholds, rejection events, task execution/timeout warnings, and task waiting time warnings.

Project Links

Gitee: https://gitee.com/dromara/dynamic-tp GitHub: https://github.com/dromara/dynamic-tp