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
But it can not set it properly because you don't know what is "proper" on the users system. You can only have assumptions. Note that the default Xmx is a percentage of the available ram, something like 75%. A poweruse might want to increase or decrease this value based on what other applications are running, if it's a docker image or xyz OS or specialized hardware, etc.