-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
15
-
x86_64
-
windows
A DESCRIPTION OF THE PROBLEM :
The Windows implementation of sun.net.dns.ResolverConfigurationImpl starts a daemon thread in its static initializer block [1].
Unfortunately, no explicit thread name is defined so the thread name is typically "Thread-<number>".
Defining no explicit thread name can make ones life harder, for example when monitoring the application or when writing a thread leak detection.
In this request for enhancement I would like to suggest to define an explicit thread name that makes it easier to tell the address listener thread apart from other threads.
I would be happy to submit a patch if such a change is welcomed by the project.
[1]: https://github.com/openjdk/jdk/blob/3b350ad87f182c2800ba17458911de877ae24a6d/src/java.base/windows/classes/sun/net/dns/ResolverConfigurationImpl.java#L198
The Windows implementation of sun.net.dns.ResolverConfigurationImpl starts a daemon thread in its static initializer block [1].
Unfortunately, no explicit thread name is defined so the thread name is typically "Thread-<number>".
Defining no explicit thread name can make ones life harder, for example when monitoring the application or when writing a thread leak detection.
In this request for enhancement I would like to suggest to define an explicit thread name that makes it easier to tell the address listener thread apart from other threads.
I would be happy to submit a patch if such a change is welcomed by the project.
[1]: https://github.com/openjdk/jdk/blob/3b350ad87f182c2800ba17458911de877ae24a6d/src/java.base/windows/classes/sun/net/dns/ResolverConfigurationImpl.java#L198