#VirtualThreads changed significantly in JDK 24 & 25.
JEP 491 fixes monitor pinning, but new bottlenecks emerge in connection pools, rate limiters, and ThreadLocal caches that no longer behave as expected.
This #InfoQ article explains what to audit before adopting virtual threads, with guidance backed by a public benchmark.
🔗 Read more: https://bit.ly/4g8tmZl
JDK 24 removed the monitor-related carrier-thread pinning that stalled Netflix and similar teams on Java 21. What has replaced it on JDK 25 LTS is downstream-resource saturation: The bottleneck moved and now demands explicit bounding in application code. This article maps the failure modes that surface after virtual-thread adoption and gives a practical sequence backed by a public benchmark.
bit.ly
Comments (0)