imbajin opened a new pull request, #818: URL: https://github.com/apache/hugegraph-toolchain/pull/818
## Purpose of the PR During Hubble shutdown, Spring closed the application context but idle async workers kept the JVM alive. The executor was initialized manually and was not registered as a Spring bean. ## Main Changes Register the existing async executor with Spring so the container initializes and closes it. Its pool sizing, queue capacity and `AsyncConfigurer` interface stay unchanged. Document executor ownership in the Hubble README. Before: context closes → idle worker pool remains alive. After: context closes → the managed worker pool shuts down. This is a separate executor-lifecycle follow-up to the Loader cleanup in [apache/hugegraph-toolchain#814](https://github.com/apache/hugegraph-toolchain/pull/814). It does not change active import cancellation or task persistence. ## Verifying these changes - [ ] Trivial rework / code cleanup without any test coverage. (No Need) - [ ] Already covered by existing tests. - [x] Need tests and can be verified as follows: - A real Spring context dispatches work through `@Async`; after the work drains, context closure terminates the pool and its workers. The test reproduces the failure with the original configuration. - Affected reactor compilation, Client/Loader/Hubble unit suites, formatting and Checkstyle passed. The final test cleanup adjustment passed its targeted test and style checks. - Three independent reviewers checked the final change and its validation boundaries. ## Does this PR potentially affect the following parts? - [ ] Nope - [ ] Dependencies (add/update license info) - [ ] Modify configurations - [ ] The public API - [x] Other affects: application async executor lifecycle ## Documentation Status - [ ] `Doc - TODO` - [x] `Doc - Done` - [ ] `Doc - No Need` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
