JDK-8316250 : scaleability: some events not optimized with should_post_xxx functions
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: jvmti
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2023-09-14
  • Updated: 2024-10-15
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 25
25Unresolved
Related Reports
Relates :  
JDK-8312174 - missing JVMTI events from vthreads parked during JVMTI attach
Description
The fix of:
  8312174 missing JVMTI events from vthreads parked during JVMTI attach
enabled a mechanism to conditionally create a JvmtiThreadState with a call to function java_thread->get_jvmti_thread_state() lazily at the point when a JVMTI event is posted. It caused some event posting code to create JvmtiThreadState's even though the events have not been enabled. Using preliminary should_post_xxx function calls will fix this issue.
One example is vmtiExport::post_exception_throw(). Need to check if there are more such events.