Hippo4j changes thread pool parameters while the JVM keeps serving
Asynchronous thread pool framework supporting dynamic thread pool changes, monitoring and alarms, easy to adopt without modifying your code.
At a glance
- What is it?
- Hippo4j wraps a Java thread pool so core threads, maximum threads, queue capacity and the rejection policy can be edited at runtime, with four built-in alarm types and adapters for container and framework pools. Client support is verified only through Spring Boot 2.7.5, and the newest tagged release is from April 2023.
- Who is it for?
- This fits services that cannot restart to change a pool and run on a supported Spring Boot version. It is untested on Spring Boot lines past 2.7.5, and no rollback procedure for an approved change is written down in the README.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 8 months ago.
- What is it written in?
- Mainly Java, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- opengoofy/hippo4j5,999 ★ · -2
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| opengoofy/hippo4j | 6k | 6k |
-2 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Four pool parameters can change under a running JVM
A plain ThreadPoolExecutor is configured with core threads, maximum threads, queue capacity and the rejection handler at construction time. Hippo4j exists to move those four values afterwards, and the console edits them for a registered pool while traffic keeps arriving. No code change and no redeploy is involved, which is the pitch in one line. The problem the project writes down underneath that feature is concrete: pools get defined carelessly, thread counts climb, and the server takes the load. Worse, the values are hard to judge before concurrency arrives, so a console makes them adjustable without making them obvious. Queue capacity and the rejection strategy belong together because a backed up queue is what pushes a pool into refusing new work.
Four alarm channels, and no stated destination for them
Hippo4j names four built-in notification strategies: pool activity, capacity watermark, the rejection policy, and task execution time running long. A native pool only makes noise at the moment it rejects work, by which point the backlog has already disturbed traffic that was fine a minute earlier. Splitting the signal into four channels means a queue that fills slowly can be reported before the rejection counter moves at all. The fourth channel catches something an application log never reports on its own: a task that takes far longer than its neighbours. The README does not say where these notifications are delivered, so the project page alone cannot confirm that a threshold will reach anyone.
Context handoff and bounded shutdown, filed under extension
Two items on the problem list are plain Java plumbing rather than observability. The first is context: values placed in MDC do not survive a hand-off to a worker thread, so a request identifier the logging setup depends on is gone once the task is queued. Hippo4j supports passing context into thread pool tasks so that identifier keeps flowing. The second is shutdown. A stock pool drops queued work when the process closes, and the project treats that as a defect worth fixing: it can wait for the pool to finish its tasks within a time you specify before the application exits. Both of these are filed under feature extension rather than dynamic change, so they belong to the client wrapper and not to the console.
Two server modes, and one of them needs middleware
The console needs somewhere to hold pool state, and the project offers two shapes for it: one that depends on a configuration center, and one with no middleware dependency. The no-middleware mode is not a properties file. The project says it borrowed the shape of configuration and registry projects such as Nacos and Eureka to build a lightweight equivalent, and wrote a custom RPC layer over Netty to carry the client and server conversation. A server process therefore still has to exist and be reachable, and the community image hippo4j/hippo4j-server is how that process is published. Both modes are explained on the documentation site rather than in the README, and the README does not compare their operational cost.
Container and framework pools come in through adapters
Hippo4j does not limit itself to pools the application created. Tomcat, Jetty and Undertow container pools can be watched at runtime and have their thread counts changed. The same treatment covers framework and messaging pools: Dubbo, Hystrix, RabbitMQ and RocketMQ report consumer pool data and accept thread count changes. That is the difference between this and a metrics exporter. An exporter shows a container queue depth and leaves you to act; an adapter lets you move a thread count up or down while requests are being served. The cost is that each adapter is one integration point tied to a version of the framework it wraps, and the README gives no compatibility table for those versions.
Admin approval gates the edit, but nothing gates the undo
Pool parameters are treated as production change requests. Hippo4j supports several user roles, and an edit from an ordinary user needs an Admin to approve it before it takes effect, which makes a live change to core threads or queue capacity a reviewable event instead of a silent one. Plugins follow the same pattern in spirit: built-in pool plugins can be extended at runtime and users are invited to write their own. What the approval buys is authorship, not reversibility. The README describes no rollback procedure, names no role other than Admin, and does not say how long a queued approval sits before someone reviews it or whether an approved edit can be returned to previous values from the console.
Verified only through Spring Boot 2.7.5, with the newest tag from 2023
The one hard boundary the project states is client compatibility: Spring Boot 1.5.x through 2.7.5 is tested, and higher versions are explicitly not tested. That ceiling matters more than any feature named above it, because the console can change parameters for a pool that a newer framework line never agreed to expose. Release timing adds a second question. The newest tagged release is 1.5.0 from April 15, 2023, preceded by 1.4.3 in November 2022 and 1.4.2 in October 2022, while the default branch is develop and its last push is dated March 12, 2026. The README also carries no install command and no JDK requirement, so the pieces have to be traced from these paths:
opengoofy/hippo4j (branch develop, Apache-2.0)
homepage https://hippo4j.github.io
quick start https://hippo4j.cn/docs/user_docs/user_guide/quick-start
server image hippo4j/hippo4j-server
demo console http://console.hippo4j.cn/index.html
.codecov.yml
.github/
.gitignore
.mvn/
.vscode/
LICENSE
README-EN.md
README.md
agent/
checkstyle/
dependencies/
docker/
docs/
examples/
examples/pom.xml
examples/threadpool-example/
format/
infra/
kernel/
lombok.config
node_modules/
pom.xml
starters/
tests/
threadpool/For a first look, the documentation site carries the quick start path and the demo console shows the interface before anything is installed in production.
Editorial conclusion
This fits services that cannot restart to change a pool and run on a supported Spring Boot version. It is untested on Spring Boot lines past 2.7.5, and no rollback procedure for an approved change is written down in the README.
Frequently asked questions
What can Hippo4j change in a thread pool while the application runs?
Core threads, maximum threads, queue capacity and the rejection policy, edited from the console for a registered pool instance without a code change or a redeploy.
Which Spring Boot versions does the Hippo4j client support?
The client is tested from Spring Boot 1.5.x through 2.7.5. Higher versions are not tested, so anything past that line is unverified.
How does Hippo4j handle MDC context and shutdown?
It supports passing context into thread pool tasks so MDC values survive the thread hand-off, and it can wait for pool tasks to finish within a set time when the project closes.
Does Hippo4j need a configuration center to run?
It ships two modes, one that depends on a configuration center and one with no middleware dependency. The server itself is published as the hippo4j/hippo4j-server image.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/opengoofy-hippo4j)Star history chart for your README
[](https://hysenlabs.com/projects/opengoofy-hippo4j)Was this useful?