// the find
opengoofy/hippo4j
📌 异步线程池框架，支持线程池动态变更&监控&报警，无需修改代码轻松引入。Asynchronous thread pool framework, support Thread Pool Dynamic Change & monitoring & Alarm, no need to modify the code easily introduced.
Hippo4j is a Java library for managing thread pools dynamically at runtime — change core/max threads, queue capacity, and rejection policies without restarting the JVM. It targets Spring Boot services running in high-concurrency environments where thread pool misconfiguration causes production incidents. There are two modes: standalone (config-center-based) and a server mode with its own management console.
The dynamic parameter change at runtime is the real value — you can tune a thread pool under load without a deploy. MDC context propagation across thread boundaries is included, which most people bolt on manually and get wrong. The framework adapters for Tomcat, Dubbo, RocketMQ, and RabbitMQ consumer pools mean you can actually observe the pools that bite you in production, not just the ones you created yourself. The Java agent mode lets you attach to existing applications without adding a Spring Boot dependency, which matters for teams that can't touch the application code.
SpringBoot version support tops out at 2.7.5 per the docs — Spring Boot 3.x and the Jakarta namespace migration aren't confirmed working, which rules it out for anyone on a current stack. The server mode means you're running yet another piece of infrastructure (their custom console + server) just to manage thread pools — that's a hard sell when you already have Prometheus and Grafana. The README is almost entirely in Chinese, and while an English translation exists, the docs site and issue tracker are primarily Chinese-language, so debugging problems or tracking releases requires translation overhead. Last commit was March 2026 but activity looks sparse; the project's energy appears redirected toward a new AI project advertised in the README itself.