-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
javax.naming.directory.InitialDirContext fails on windows #4304
Comments
Please add the |
Hi I am also affected with this issue. Is there any workaround? |
@Saljack, you can use following [
{
"name":"sun.net.dns.ResolverConfigurationImpl",
"fields":[
{"name":"os_searchlist"},
{"name":"os_nameservers"}
]
}
] in conjunction with |
Thanks for your suggestion, it is really helpful for resolving my problem. Let me paste my error message to help the search engine to locate this page |
Hello Team, I am also encountering this issue. Thank you, happy new year!!! |
at sun.net.dns.ResolverConfigurationImpl.stringToList(ResolverConfigurationImpl.java:69) oracle/graal#4304
…ilation on Windows
Apply a workaround for oracle/graal#4304
Apply a workaround for oracle/graal#4304
Describe the issue
Essentially on windows image you will get
NPE
from:Steps to reproduce the issue
Test code and GH Actions runs can be found from https://github.com/jvalkeal/win-netty-issue. There doesn't seem to be any issues on macos/linux, just when running native on windows. Matrix build shows that
java Test
runs ok buttest.exe
doesn't.Describe GraalVM and your environment:
More details
This was originally reported and discussed as a
netty
issue as it looks to initiate call to this stack.spring-attic/spring-native#1319
spring-projects/spring-framework#27749
However looks like for some reason https://github.com/openjdk/jdk/blob/a9a271179d2a7952154b7509a999b100cc98b13c/src/java.base/windows/classes/sun/net/dns/ResolverConfigurationImpl.java#L101 doesn't initialize class fields via native call, thus the NPE. Or at least that's where my debugging skills stopped.
The text was updated successfully, but these errors were encountered: