Inside Project Loom’s Thread Scheduler: How Carrier Threads Get Pinned
Overview The Scheduling Contract Between Virtual and Carrier Threads What Actually Causes a Carrier Thread to Get Pinned?
Java News | Enterprise Java & Spring
Java News covers enterprise Java development, Spring Boot, and JVM performance.
Overview The Scheduling Contract Between Virtual and Carrier Threads What Actually Causes a Carrier Thread to Get Pinned?
As of: March 22, 2026 — Azul Zulu Prime 24.03 Quick nav Why does the SIGILL only fire after a CRaC restore? What does the crash look like in a…
Java 21 made virtual threads a permanent language feature, ending a multi-year preview cycle and giving the JVM its first real answer to high-concurrency.
I still remember the day my team hit a wall with our CI pipeline. We were maintaining a massive Spring Boot monolith—over 80 modules, half a million lines.
So there I was last Tuesday, staring at the "Gradle: Syncing..." spinner for the fourth time before 9 AM. My M2 MacBook Pro sounded like it was preparing.
I read another comment thread yesterday where someone confidently claimed Java is too bloated for CLI tools or edge devices. Learn about Java ME news.
I spent last weekend staring at Datadog dashboards, watching our Java microservices take their sweet, agonizing 14 seconds to spin up during a sudden.
Well, I have to admit, I was wrong about that Java 25.0.2 upgrade causing our memory issues. Actually, let me back up — the real culprit was a single.
I spent three hours yesterday tracing a dropped database connection in a reactive pipeline. The stack trace was completely useless, pointing to a thread.
Actually, I distinctly remember sitting in that conference room in 2019, watching my colleague demo a high-throughput service written in Go.