0 views collected around this technical thread.
This article explains the six Java thread states defined in Thread.State, demonstrates how to use the Arthas diagnostic tool to identify blocked, waiting, or timed‑waiting threads, and provides practical strategies for diagnosing and optimizing thread‑blocking issues in Java applications.
This article explains the six Java thread states defined in java.lang.Thread.State, describes the meaning of each state, illustrates the possible state transitions, and provides three runnable code examples that demonstrate NEW, RUNNABLE, BLOCKED, WAITING, TIMED_WAITING and TERMINATED states along with their console outputs.
This article explains the fundamental concepts of processes and threads, their relationship, resource allocation, scheduling, communication methods, practical use cases, and interview preparation tips, helping readers choose between multiprocessing and multithreading for various scenarios.
This article examines why a thread may remain in an uninterruptible wake‑up state during system suspend, explains deadlock fundamentals, outlines thread lifecycle states, and provides practical debugging steps and mitigation strategies using Java concurrency tools and system monitoring.
This article explains how the Java Memory Model defines the interaction between threads, thread stacks, and the heap, illustrates these concepts with diagrams and example code, and discusses how modern hardware memory architecture, caches, and CPU registers affect visibility and race conditions in concurrent Java programs.
This article introduces nine different approaches to achieve asynchronous programming in Java, including using Thread and Runnable, Executors thread pools, custom thread pools, Future and Callable, CompletableFuture, ForkJoinPool, Spring @Async, message queues, and Hutool's ThreadUtil, with code examples and usage tips.
The article outlines nine practical approaches for asynchronous programming in Java—including low‑level Thread/Runnable, managed Executors and custom thread pools, Future/Callable, CompletableFuture, ForkJoinPool, Spring’s @Async annotation, message‑queue integration, and the Hutool ThreadUtil utility—offering a comprehensive toolbox for scalable, non‑blocking execution.
This article investigates whether the JVM terminates when a thread encounters an OutOfMemoryError, demonstrating through Spring Boot controllers and multithreaded examples how main and child threads, daemon settings, and explicit OOM handling affect JVM shutdown behavior.
This article explains why asynchronous programming boosts Java application performance and walks through seven practical methods—Thread, FutureTask, CompletableFuture, Guava ListenableFuture, EA‑Async, Cactoos, and Jcabi‑Aspects—each illustrated with complete, runnable code examples.
This article explains why C++ timers are essential for asynchronous programming, presents three implementation approaches—including a simple thread‑chrono version, a Boost.Asio based timer, and a C++11 atomic/condition‑variable design—offers practical optimization tips such as precise intervals, thread‑pool reuse, efficient callbacks, and memory management, and demonstrates their impact with a network‑server case study comparing naïve and optimized solutions.
This article explains three common ways to create multithreaded Java programs—extending Thread, implementing Runnable, and using Lambda expressions—providing step‑by‑step instructions, code samples, console output, and a summary of each method’s advantages and appropriate use cases.
The article explains why forcibly stopping a Java thread is unsafe, outlines common scenarios requiring thread exit, compares graceful and forced termination methods, and provides practical techniques such as flag checks and Thread.interrupt() with recommended interrupt‑handling strategies.
This article explains how Java handles uncaught exceptions in threads, demonstrates setting per‑thread, thread‑group, and global exception handlers, and provides complete code examples illustrating each approach along with their execution results.
This article introduces eight common Java asynchronous implementation techniques—including raw threads, Future, CompletableFuture, Spring @Async, ApplicationEvent, message queues, third‑party utilities like Hutool ThreadUtil and Guava ListenableFuture—explaining their usage, code examples, advantages, and drawbacks for improving performance in scenarios such as sending SMS or emails.
The article clarifies Java processes and threads using a game analogy, then demonstrates three thread‑creation techniques—extending Thread, implementing Runnable, and implementing Callable with FutureTask—while covering run vs start, thread control methods such as sleep, join, and daemon settings.
The article explains why forcibly stopping a Java thread is unsafe, outlines common scenarios that require thread exit, compares graceful and forced termination, and presents practical techniques such as flag checks and Thread.interrupt() to achieve safe and predictable thread shutdown.
Both wait() and sleep() can pause a thread and enter waiting states, but wait() belongs to Object and requires synchronized blocks, releases the monitor lock, and must handle spurious wakeups, whereas sleep() is a Thread method that does not release locks and has simpler usage.
Explore the fundamentals and advanced techniques of asynchronous programming in Java, from basic thread creation and thread pools to Future, FutureTask, CompletableFuture, and Spring Boot’s @Async annotation, including practical code examples, event handling, and message queue integration for high‑throughput systems.
An OutOfMemoryError does not always terminate the JVM; the JVM exits only when all non‑daemon threads have finished or the operating system kills the process, so proper exception handling and thread management are essential to keep the application alive.
The deprecated Thread.stop method should never be used; instead, Java threads are stopped gracefully by using a volatile stop flag or interrupting blocked threads, handling InterruptedException, and distinguishing between Thread.isInterrupted() (read‑only) and Thread.interrupted() (clears the flag).