-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
cannot launch jnlp on windows due to exception while creating native storage directory #570
Comments
Hi,
|
Thanks - this seems to be another workaround 👍 But I wonder why the application-files are created this way. 🤔 |
I stumbled across the same problem. Saw the same kind of restricted permissions and |
I haven't checked the code how ows/itw creates the file but it would be nice if even manually created temp-folder would work out of the box. If I manually create a file in this folder I can rename it without issues. If the current implementation is because of security reasons a better error-message would be helpful because ot took some time to find the cause. |
Problem/bug still present in v 1.10.1. EDIT: |
I've created another issue in AdoptOpenJDK/IcedTea-Web#955 - hopefully it get's more attention there. |
OWS/IcedTea-Web creates a temp-folder netx-native-xxxx.temp and tries to rename it which does not work if the folder has "insufficient" permissions.
The default %TEMP% (%LOCALAPPDATA%\Temp) has (at least on my system) this ACLs
If you create another temp-directory like C:\temp\ows the ACLs are slightly different
As you can see in the default temp-folder the current user has an ACL that grant full access.
In the created folder c:\temp\ows there are only group rights set.
In BOTH directory I can create folder an files in windows explorer.
But launching a jnlp works only in the default temp-folder - not in c:\temp\ows
to reproduce this, create the folder c:\temp\ows
open a command prompt and run
This results in an exception during startup
workaround: give current user full access to c:\temp\ows
The text was updated successfully, but these errors were encountered: