wrapper.environment.dump.loglevel

Compatibility :3.5.36
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/OSIBM z/Linux

It is sometimes useful to dump all of the environment variables visible to the Wrapper, along with where the values originated. This property controls the log level at which this dump will be logged. The default value is DEBUG, meaning that it will be included in debug output.

It is fairly common that users have problems with their environment not being what was expected. This property can be very powerful in helping to track down the source of such problems.

When running as a service on Windows XP or Windows Server 2003, the Wrapper will load all declared system-wide environment variables stored in the registry when the Wrapper is first started. If the USERNAME environment variable is defined, the Wrapper will then load the environment for that user from the registry as well. This is done to make it possible to make changes to the configured environment and then make use of them without requiring a system reboot.

Originally, this reloading of the registries was done on all Windows versions. Since Wrapper version 3.5.5, this was disabled for Windows XP/Server 2003 and above. In Wrapper version 3.5.16, the reloading was re-enabled for Windows XP and Server 2003, but left disabled for more recent versions of Windows where it is no longer necessary.

On UNIX, it is common for the Wrapper to have close to an empty environment when launched on system startup.

Example:
wrapper.environment.dump.loglevel=INFO

The debug output starts with a source column which shows where the environment was set. The values, left-to-right, show the order of the sources from which they can be set. The final value will be used.

  • P - Defined in the parent process, i.e. the variable was set when the Wrapper was launched.
  • S - Defined in the system-wide Registry. (Only for versions of Windows older than XP/Server 2003)
  • A - Defined in the account-specific Registry. (Only for versions of Windows older than XP/Server 2003)
  • W - Defined by the Wrapper on startup.
  • C - Defined within the Wrapper configuration file.

The following is an example of the environment output when run on Windows as a specified user. Note that some of the variables are configured by the system, others by the Wrapper, or Wrapper configuration, and yet others are loaded from the registry both for the SYSTEM user and configured account.

Example:
wrapper  | Environment variables (Source | Name=Value) BEGIN:
wrapper  |   P---- | ALLUSERSPROFILE=C:\Documents and Settings\All Users
wrapper  |   P---- | ANT_HOME=C:\Apache\apache-ant-1.7.1
wrapper  |   P---- | APPDATA=C:\Documents and Settings\me\Application Data
wrapper  |   P---- | CommonProgramFiles=C:\Program Files\Common Files
wrapper  |   P---- | CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
wrapper  |   P---- | COMPUTERNAME=MYPC
wrapper  |   P---- | ComSpec=C:\WINDOWS\system32\cmd.exe
wrapper  |   ----C | FOO=Bar
wrapper  |   P---- | FP_NO_HOST_CHECK=NO
wrapper  |   P---- | J2D_D3D=false
wrapper  |   P---C | JAVA_HOME=Foobar
wrapper  |   P---- | LOGONSERVER=\\MYPC
wrapper  |   P---- | NUMBER_OF_PROCESSORS=1
wrapper  |   P---- | OS=Windows_NT
wrapper  |   P---- | Path=C:\Sun\jdk1.6.0_10_x64\bin\;C:\Apache\apache-ant-1.7.1\bin\;C:\WINDOWS\system32; ...
wrapper  |   P---- | PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.RB;.RBW
wrapper  |   P---- | PROCESSOR_ARCHITECTURE=AMD64
wrapper  |   P---- | PROCESSOR_IDENTIFIER=EM64T Family 6 Model 23 Stepping 6, GenuineIntel
wrapper  |   P---- | PROCESSOR_LEVEL=6
wrapper  |   P---- | PROCESSOR_REVISION=1706
wrapper  |   P---- | ProgramFiles=C:\Program Files
wrapper  |   P---- | ProgramFiles(x86)=C:\Program Files (x86)
wrapper  |   P---- | SESSIONNAME=Console
wrapper  |   P---- | SystemDrive=C:
wrapper  |   P---- | SystemRoot=C:\WINDOWS
wrapper  |   P---- | TEMP=C:\Documents and Settings\me\Local Settings\Temp
wrapper  |   P---- | TMP=C:\Documents and Settings\me\Local Settings\Temp
wrapper  |   P---- | USERDOMAIN=MYPC
wrapper  |   P---- | USERNAME=me
wrapper  |   P---- | USERPROFILE=C:\Documents and Settings\me
wrapper  |   P---- | windir=C:\WINDOWS
wrapper  |   ---W- | WRAPPER_ARCH=x86
wrapper  |   ---W- | WRAPPER_BIN_DIR=C:\myapp\bin
wrapper  |   ---W- | WRAPPER_BITS=64
wrapper  |   ---W- | WRAPPER_FILE_SEPARATOR=\
wrapper  |   ---W- | WRAPPER_HOST_NAME=MYPC
wrapper  |   ---W- | WRAPPER_HOSTNAME=MYPC
wrapper  |   ---W- | WRAPPER_OS=windows
wrapper  |   ---W- | WRAPPER_PATH_SEPARATOR=;
wrapper  |   ---W- | WRAPPER_PID=504
wrapper  |   ---W- | WRAPPER_WORKING_DIR=C:\myapp\bin
wrapper  | Environment variables END:

NOTE

Since Wrapper version 3.5.36 the dump of environment variables can occur each time the configuration is reloaded if wrapper.restart.reload_configuration is set to TRUE. Previously, this was only done on startup.

wrapper.environment.dump

Compatibility :3.5.0
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/OSIBM z/Linux

WARNING

Use of this property has been deprecated as of Wrapper version 3.5.36 in favor of the wrapper.environment.dump.loglevel property.