asmhatre/java-core-examples
1
0
Fork 0
Code Activity

concurrency-interview: companion code for the Top 40 interview post

Browse Source 
Adds the concurrency-interview module: a real race condition with its
actual lost-update count, why volatile alone doesn't fix it, a real
JVM-detected deadlock (ThreadMXBean.findDeadlockedThreads()) with the
fix, and ScopedValue's exact child-thread inheritance rules (finalized
in JDK 25 via JEP 506, demonstrated against StructuredTaskScope, still
preview per JEP 505/525). 4 runnable demos, 1 JUnit test class (9
tests), 5 captured output transcripts.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01FhzLY5p6okFva3qsnsRyvM
This commit is contained in:
asmhatre
2026-09-30 07:25:12 +00:00
co-authored by Claude Sonnet 5
parent bc5153d2a5
commit 202f2f18a5
15 changed files with 553 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
concurrency-interview/output/03-deadlock-detection.txt
+12
View File
@@ -0,0 +1,12 @@
=== Opposite lock order: a real deadlock, detected via ThreadMXBean ===
thread-1: holding lockA, waiting for lockB
thread-2: holding lockB, waiting for lockA
main: findDeadlockedThreads() detected 2 deadlocked threads
thread-1 is blocked on java.lang.Object@5451c3a8, owned by thread-2
thread-2 is blocked on java.lang.Object@49476842, owned by thread-1
=== Same lock order on both threads: no deadlock possible ===
thread-1 (fixed order): acquired both locks, done
thread-2 (fixed order): acquired both locks, done
main: both fixed-order threads finished, isAlive t1=false t2=false
done (the process exits here - the two deadlocked threads above never finish)