| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8289868 | 20 | Alan Bateman | P3 | Resolved | Fixed | b06 |
| JDK-8291387 | 19.0.2 | Alan Bateman | P3 | Resolved | Fixed | b01 |
| JDK-8291224 | 19.0.1 | Alan Bateman | P3 | Resolved | Fixed | b04 |
The description of the ThreadStart/End events needs to re-visited to more clearly explain if these events are sent for virtual threads, the difference between these events and the VirtualThreadStart/End events, and the connection to the can_support_virtual_threads capability.
The spec needs to make it clear that agents that enable ThreadStart and/or ThreadEnd, but do not enable the can_support_virtual_threads capability, will receive these events for virtual threads.
On the other hand, if the can_support_virtual_threads capability is enabled, the events for virtual threads are VirutalThreadStart and VirutalThreadEnd so a "virtual thread aware" agent gets fine control on the the events and can use the same or a different callback for these events.
The spec needs to make it clear that agents that enable ThreadStart and/or ThreadEnd, but do not enable the can_support_virtual_threads capability, will receive these events for virtual threads.
On the other hand, if the can_support_virtual_threads capability is enabled, the events for virtual threads are VirutalThreadStart and VirutalThreadEnd so a "virtual thread aware" agent gets fine control on the the events and can use the same or a different callback for these events.
- backported by
-
JDK-8289868 Clarify relationship between ThreadStart/ThreadEnd and can_support_virtual_threads capability
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- csr for
-
JDK-8289574 Clarify relationship between ThreadStart/ThreadEnd and can_support_virtual_threads capability
-
- Closed
-
(1 links to)