JDK-8316751 : IllegalMonitorStateException: current thread is not owner
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 22
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2023-09-22
  • Updated: 2023-10-07
  • Resolved: 2023-10-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 22
22Resolved
Related Reports
Duplicate :  
JDK-8316880 - AArch64: "stop: Header is not fast-locked" with -XX:-UseLSE since JDK-8315880
Relates :  
JDK-8315880 - Change LockingMode default from LM_LEGACY to LM_LIGHTWEIGHT
Relates :  
JDK-8291555 - Implement alternative fast-locking scheme
Description
We have seen "IllegalMonitorStateException: current thread is not owner" on aarch64 while running SPECjvm2008/compiler.sunflow.
May be the same or a similar issue as others related to JDK-8315880.
Comments
Reclosing as duplicate of JDK-8316880.
04-10-2023
Only bugs associated with changesets should be closed as "Fixed".
04-10-2023
Problem is gone since JDK-8316880.
04-10-2023
Could you test again now that JDK-8316880 is merged?
03-10-2023
"java -XX:+PrintFlagsFinal -version |grep LSE" says: bool UseLSE = false {ARCH product} {default}
25-09-2023
Is UseLSE enabled on this machine? If not it's likely the same cause as JDK-8316880.
25-09-2023