-
Notifications
You must be signed in to change notification settings - Fork 52
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
'Access denied' in executable packaged with jPackage when tries to start a SubProcess using Kernel32.CreateProcess() #171
Comments
Thank you for bringing this to our attention. Would you be able to provide a small reproducer? |
Many thanks for the fast reply! |
Okay, mostly I just want to figure out if this is a runtime problem for the JDK, or an effect of how the application is packaged. |
I verified it: In the Task-Manager I can see that the used JRE is the 17.0.10. |
Okay, looked around at the commit logs and this is the only change (of four) that touched anything related to windows in
I've no experience with |
Hi William, |
Hi William, |
We've got a problem with amazon-corretto-17.0.10.7.1-windows-x64-jdk: Our application gets packed to an executable and tries to start a subprocess using kernel32.CreateProcess(...)
Until amazon-corretto-17.0.9.8.1-windows-x64-jdk everything works fine, now we get an 'Access denied'.
If I run my application out of the debugger of the IDEA, also everything works fine.
Steps to reproduce: Not sure if it happens every time if you package a java-application into an executable and start a sub-process.
Expected behavior: Sub-Process (e.g.calc.exe) is started
OS: Windows 10 with amazon-corretto-17.0.10.7.1-windows-x64-jdk
boolean result = kernel32.CreateProcess(null, 'calc.exe, null, null, true, new WinDef.DWORD(CREATE_SUSPENDED | CREATE_BREAKAWAY_FROM_JOB | CREATE_UNICODE_ENVIRONMENT), environment, 'c:\test' si, pi);
Result is: Kernel32Util.getLastErrorMessage() is 'Access denied'
Unfortunately, I don't know if I could debug the Exe-Process, and there is no further stacktrace.
The text was updated successfully, but these errors were encountered: