Discovering a JDK Race Condition, and Debugging it in 30 Minutes with Fray

Discovering a JDK Race Condition, and Debugging it in 30 Minutes with Fray I’ve been adding more integration tests for Fray recently. To ensure Fray can handle different scenarios, I wrote many creative test cases. Many of them passed as expected, while some failures led to epic fixes in Fray. Then something unexpected happened: Fray threw a deadlock exception while testing the following seemingly innocent code: 1private void test() { 2 ScheduledThreadPoolExecutor executor = new ScheduledThreadPoolExecutor(1); 3 // Shutdown thread. 4 new Thread(() -> { 5 executor.shutdown(); 6 }).start(); 7 try { 8 ScheduledFuture<?> future = executor.schedule(() -> { 9 Thread.yield(); 10 }, 10, TimeUnit.MILLISECONDS); 11 try { 12 future.get(); 13 Thread.yield(); 14 } catch (Throwable e) {} 15 } catch (RejectedExecutionException e) {} 16} This code creates a ScheduledThreadPoolExecutor, schedules a task, and shuts down the executor in another thread. Initially, I suspected a bug in Fray, but after investigation, I discovered that the deadlock was actually caused by a bug in the JDK itself.

JEP 519: Compact Object Headers

JEP 515: Ahead-of-Time Method Profiling

Jobs at Overture Rede

Everyone at Overture Rede is free to explore and work the way you want. Come join us!

InfoQ Dev Summit Boston 2025 | Are You Missing a Data Frame? The Power of Data Frames in Java

There is a missing tool in your Java data structure toolkit – Data Frames!

Hire Java Developers to Build Modern & High-Performance Apps

Don't just fill a role, find your perfect fit. Hire dedicated Java developers for your project. Scale your team seamlessly, get started now!

Which is the Right Tech in 2025? Node.js or Java?

Node.js vs Java: Which to choose in 2025?

OpenJDK JDK 24.0.1 GA Release