JDK-8175078 : Release Note: os::set_native_thread_name() cleanups
- Type: Sub-task
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 8u351,9
- Priority: P4
- Status: Closed
- Resolution: Delivered
- Submitted: 2017-02-16
- Updated: 2022-09-16
- Resolved: 2017-05-01
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.
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 8 | JDK 9 |
|---|---|
| 8u351Resolved | 9Resolved  |
Description
On platforms that support the concept of a thread name on their native threads, the `java.lang.Thread.setName()` method will also set that native thread name. However, this will only occur when called by the current thread, and only for threads started through the `java.lang.Thread` class (not for native threads that have attached via JNI). The presence of a native thread name can be useful for debugging and monitoring purposes. Some platforms may limit the native thread name to a length much shorter than that used by the `java.lang.Thread`, which may result in some threads having the same native name.
Comments
|