RFR: 8366659: ObjectMonitor::wait() liveness problem with a suspension request [v17]

Daniel D. Daugherty dcubed at openjdk.org
Fri Jan 16 22:28:53 UTC 2026


On Mon, 24 Nov 2025 10:22:12 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:

> The thread was picked as a successor and then suspended. It feels like it has to be qualified same as a thread owns the monitor and suspended. 

The successor protocol is an internal implementation detail of ObjectMonitor. It is NOT exposed
to person debugging their Java program. Just because a suspend thread is marked as  the
successor, that does NOT mean it should prevent other non-suspended threads from entering
the monitor. In other words, being the successor IS NOT the same as owning the monitor.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/27040#issuecomment-3762044144


More information about the hotspot-runtime-dev mailing list