One three-round worker pipeline implemented with CountDownLatch (one latch per round), CyclicBarrier (reusable, with a barrier action), and Phaser (reusable, plus dynamic mid-run registration), alongside Semaphore solving the genuinely different problem of bounding concurrent access. Covers timeout behavior (CyclicBarrier permanently breaks on one timeout, Phaser doesn't) and virtual-thread compatibility, including the corrected finding that Object.wait() releases its monitor and never pinned, unlike Thread.sleep() inside synchronized. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01FhzLY5p6okFva3qsnsRyvM
17 lines
1.2 KiB
Plaintext
17 lines
1.2 KiB
Plaintext
$ java SemaphoreResourceGuard
|
|
|
|
worker-0 round 1: acquired permit, 1 callers concurrently in the resource (availablePermits=0)
|
|
worker-1 round 1: acquired permit, 2 callers concurrently in the resource (availablePermits=0)
|
|
worker-2 round 1: acquired permit, 2 callers concurrently in the resource (availablePermits=0)
|
|
worker-3 round 1: acquired permit, 2 callers concurrently in the resource (availablePermits=0)
|
|
worker-3 round 2: acquired permit, 1 callers concurrently in the resource (availablePermits=1)
|
|
worker-0 round 2: acquired permit, 2 callers concurrently in the resource (availablePermits=0)
|
|
worker-1 round 2: acquired permit, 1 callers concurrently in the resource (availablePermits=1)
|
|
worker-2 round 2: acquired permit, 2 callers concurrently in the resource (availablePermits=0)
|
|
worker-2 round 3: acquired permit, 1 callers concurrently in the resource (availablePermits=1)
|
|
worker-3 round 3: acquired permit, 2 callers concurrently in the resource (availablePermits=0)
|
|
worker-0 round 3: acquired permit, 1 callers concurrently in the resource (availablePermits=1)
|
|
worker-1 round 3: acquired permit, 2 callers concurrently in the resource (availablePermits=0)
|
|
permits=2 maxObservedConcurrency=2
|
|
done
|