350

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

Bohemian
  • 412,405
  • 93
  • 575
  • 722
Praveen Sripati
  • 32,799
  • 16
  • 80
  • 117

2 Answers2

478
informatik01
  • 16,038
  • 10
  • 74
  • 104
Bohemian
  • 412,405
  • 93
  • 575
  • 722
  • 55
    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. – paulsm4 Aug 14 '11 at 04:29
  • 1
    @Bohemian If I set property via `java -Dpropname=value` how can i then retrieve those properties? – Marek Sebera Jul 25 '13 at 10:08
  • 9
    `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. – Bohemian Jul 25 '13 at 10:13
  • 17
    Note that you can also set system properties with the environment variable `JAVA_TOOL_OPTIONS`. – flacs Oct 31 '14 at 15:19
  • Do we need JVM restart to read the updated env variable ? I know for restart required to read properties updated by external source. – Kanagavelu Sugumar May 25 '17 at 10:07
  • 7
    @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. – Bohemian May 25 '17 at 16:01
  • @paulsm4 what do you mean by "Java chose to expose OS variables as properties"? – malana Dec 11 '17 at 09:36
186

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().

Koray Tugay
  • 22,894
  • 45
  • 188
  • 319
Jake Dempsey
  • 6,264
  • 1
  • 30
  • 25
  • 8
    Finally, it's how the variables are added and the scope of the variables. – Praveen Sripati Aug 14 '11 at 12:33
  • Keep in mind that other processes can find the cmd used to launch a process, hence java system properties as well. – Christian Jun 13 '20 at 11:23
  • There is more to it. This tutorial explains in detail: https://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. – Andy Cribbens Mar 03 '21 at 10:09
  • 1
    This answer seems incorrect. Environment variables are scoped per process. Each process sees its own environment. – Pedro Lamarão Apr 07 '21 at 14:17
  • @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 Sep 14 '21 at 15:03
  • @JakeDempsey Are you sure _env variables are set in the OS (however they 'can' be set through Java)_ is a correct statement? – Koray Tugay Sep 14 '21 at 15:04
  • 1
    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. – Pedro Lamarão Sep 14 '21 at 20:57