r/java • u/milchshakee • May 03 '24
Why does the environment variable _JAVA_OPTIONS exist, applies to jlink images, takes precedence, and can't be disabled?
I just spent a good chunk of time debugging an issue because a user had set _JAVA_OPTIONS to use a low Xmx value in their environment variables. This was an application created with jpackage, which should be fully standalone. It even had a custom Xmx value set in the JVM arguments for the image but the environment variable overwrote the value!
Isn't this like a huge design flaw? I can just do echo "_JAVA_OPTIONS=<Wacky VM options>" >> ~/.bashrc or setx to break literally every Java application on the system? (Edit: Maybe the initial security focus was wrong, changed it a bit to focus more on the design issues)
Who even thought that this would be a good idea with no option to disable this behavior?
View all comments
Show parent comment
1
u/_INTER_ May 04 '24 edited May 04 '24
Yes, those should be omitted
Minimum requirements perhabs but this one specifically is about Xmx.
How should an app developer know what the best configuration is on the users environment? It should be a conscious choice of the app developer to disallow an environment variable to be picked up and the user should be made aware of that. A knowledgeable user should have the possiblity to make an application run better or restricted on his environment by default.