Story thread · 2 reports / 2 sources

Article: Virtual Threads After JDK 24: What Changed for Production Java

infoq.com · 11dShare

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. By Sandeep Bharadwaj

First report: JDK 27: The new features of Java 27 — infoworld.com, 13d