HTHou opened a new pull request, #18288: URL: https://github.com/apache/iotdb/pull/18288
## Summary - replace `SecurityManager`-based thread group selection in `IoTThreadFactory` with the current thread's group - remove the terminally deprecated `ThreadGroup.destroy()` call after procedure workers have terminated - remove the now-unused English and Chinese log message constants ## Why JDK 17 reports `SecurityManager`, `System.getSecurityManager()`, and `ThreadGroup.destroy()` as deprecated and marked for removal. These usages produced three removal warnings during compilation and would prevent smooth migration to newer JDK releases. For normal JDK 17 deployments, the thread factory behavior is unchanged because the previous non-SecurityManager path already selected `Thread.currentThread().getThreadGroup()`. Procedure shutdown behavior is also unchanged: `join()` waits for every worker to terminate before the removed `destroy()` call, and `destroy()` only affected empty thread-group metadata. ## Validation - `mvn spotless:apply -pl iotdb-core/node-commons,iotdb-core/confignode` - English `test-compile` for `node-commons` and `confignode` with `-Xlint:removal` - Chinese `test-compile` for both modules with `-P with-zh-locale` and `-Xlint:removal` - `IoTDBThreadPoolFactoryTest`: 7 tests passed - `TestProcedureExecutor`: 7 tests passed - full workspace `jdeprscan --release 17 --for-removal`: no remaining deprecated-for-removal bytecode references -- 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]
