Java system properties and environment variables

Question

What's the difference between system properties System.getProperties() and environment variables System.getenv() in a JVM?

Solution 1

I think the difference between the two boils down to access. Environment variables are accessible by any process and Java system properties are only accessible by the process they are added to.

Also as Bohemian stated, env variables are set in the OS (however they 'can' be set through Java) and system properties are passed as command line options or set via setProperty().

Solution 2

• System properties are set on the Java command line using the -Dpropertyname=value syntax. They can also be added at runtime using System.setProperty(String key, String value) or via the various System.getProperties().load() methods.
  To get a specific system property you can use System.getProperty(String key) or System.getProperty(String key, String def).

• Environment variables are set in the OS, e.g. in Linux export HOME=/Users/myusername or on Windows SET WINDIR=C:\Windows etc, and, unlike properties, may not be set at runtime.
  To get a specific environment variable you can use System.getenv(String name).

Comments

[paulsm4]

Absolutely correct, Bohemian. Environment variables are an "OS thing", and properties are a "Java thing". As it happens, Java chose to expose OS variables as properties (just as Java exposes current directory and "other stuff" as properties), but they are in fact different things.

[Praveen Sripati]

Finally, it's how the variables are added and the scope of the variables.

[Marek Sebera]

@Bohemian If I set property via java -Dpropname=value how can i then retrieve those properties?

[Bohemian]

System.grtProperties() lists all properties, and those set from command line will be there, but there's no way to distinguish those from the other properties added by the system, if that's what you're asking.

[flacs]

Note that you can also set system properties with the environment variable JAVA_TOOL_OPTIONS.

[Kanagavelu Sugumar]

Do we need JVM restart to read the updated env variable ? I know for restart required to read properties updated by external source.

[Bohemian]

@KanagaveluSugumar Yes, you need to restart: Environment variable settings are read from the environment on start up. i.e. System.getenv(String name) does not dynamically read the value from the system at call time.

[malana]

@paulsm4 what do you mean by "Java chose to expose OS variables as properties"?

[Christian]

Keep in mind that other processes can find the cmd used to launch a process, hence java system properties as well.

[Andy Cribbens]

There is more to it. This tutorial explains in detail: youtu.be/vQYfOMrdgpg - Basically env vars can also have scope, e.g. set in one shell may not be visible in another. You typically cannot set them at runtime because they are on the host, however you can set them (at runtime) in JUnit 5 using extensions etc.

[Pedro Lamarão]

This answer seems incorrect. Environment variables are scoped per process. Each process sees its own environment.

[Koray Tugay]

@PedroLamarão Are you sure? As far as I can tell environment variables are set on the host and are visible to all processes..

[Koray Tugay]

@JakeDempsey Are you sure env variables are set in the OS (however they 'can' be set through Java) is a correct statement?

[Pedro Lamarão]

The environment variable map is a per process object in Windows and every UNIX descendant. It is best to think about is a "process attribute" or some kind of process private thing. This map is created when the process is created. The initial values are set by whomever creates the process. Typically, this map shall be a copy of the creator's map. User applications are generally created by the user shell, therefore, user application's environment shall generally by a copy of the user shell's environment. There is not dynamic inheritance here, no "fall back to parent" mechanism.