0 views collected around this technical thread.
This article explains why using Thread.sleep() in Java ExecutorService unit tests is unreliable and inefficient, and introduces three robust alternatives—Future.get(), CountDownLatch, and shutdown/awaitTermination—to achieve stable and performant testing of asynchronous code.
This article explains why a Java thread pool with many waiting threads does not release resources, how calling shutdown or shutdownNow interrupts idle workers, how the ThreadPoolExecutor internals handle interruptions, and why proper shutdown is essential to allow both threads and the pool itself to be garbage‑collected.
This article explains how TCP connections are gracefully closed using the four‑way handshake, describes half‑close and half‑open states, compares the close and shutdown system calls, details the TIME_WAIT state and its impact, and offers practical techniques to reduce or avoid TIME_WAIT accumulation.
The article explains how a Java ThreadPoolExecutor can retain hundreds of waiting threads when shutdown is omitted, analyzes the GC‑root relationship of running threads, and demonstrates through code and JVisualVM screenshots that invoking shutdown or shutdownNow properly interrupts idle workers, removes them from the pool, and allows both the worker threads and the thread‑pool object to be garbage‑collected.
This article explains why Java does not provide a forced stop for threads, demonstrates how to use interrupt and various ThreadPool shutdown methods—including shutdown, isShutdown, isTerminated, awaitTermination, and shutdownNow—to safely terminate threads, and provides practical code examples.
This article presents a detailed experiment comparing graceful and kill‑9 shutdown methods on a MySQL 5.7 semi‑synchronous master‑slave cluster, analyzes their impact on data consistency, and outlines the official shutdown sequence with practical observations and recommendations for production environments.
The article thoroughly dissects Java’s ThreadPoolExecutor, explaining its constructor parameters, the ctl‑based state machine that governs thread creation, task queuing, worker locking, shutdown sequences, built‑in rejection policies, and demonstrates a real‑world extension via Vivo’s NexTask framework for high‑performance backend processing.
This article outlines Redis's key advantages such as high performance and flexible data types, discusses its limitations like lack of relational features, describes ideal in‑memory use cases, compares it with Memcached, and provides detailed instructions for shutting down, configuring, and connecting to Redis using command‑line and graphical clients.
This article provides an in‑depth analysis of Java's ThreadPoolExecutor, explaining how Executors' factory methods create pools, detailing the constructor parameters, internal state management, task submission via execute, worker thread lifecycle, and the differences between shutdown and shutdownNow, with code excerpts for clarity.