wrapper.backend.type
Compatibility :3.5.8
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxAlpine LinuxFreeBSDSolarisIBM z/Linux

The Wrapper needs to maintain constant communication between the Wrapper process and a class running within the JVM.

This communication can be configured using the following modes:

  • AUTO: use PIPE and in case of error, fallback to SOCKET
  • PIPE: use a pipe backend
  • SOCKET: use the following modes in order of priority: SOCKET_PAIR (Unix only), with fallback to SOCKET_IPv4 and then to SOCKET_IPv6
  • SOCKET_PAIR (Since ver. 3.7.0, Unix only): use a Unix domain socket pair
  • SOCKET_IPv4: use a IPv4 socket
  • SOCKET_IPv6: use a IPv6 socket

The default value is "AUTO".

Example: 
wrapper.backend.type=SOCKET

WARNING

On Unix, starting with version 3.6.0, PIPE mode uses anonymous pipes instead of named pipes for improved security.

When sensitive data, such as passwords, is transmitted over the backend channel (for example, when using wrapper.app.property.<n> properties introduced in version 3.5.57), ensuring the security of this channel is of critical importance.

On Unix, if you are using PIPE mode, upgrading to at least version 3.6.0 is strongly recommended. See vulnerability #13 for more details.

On both Windows and Unix, upgrading to version 3.7.0 further improves the overall security of the backend connection. See vulnerability #15 for more details.

Per-platform configuration

Starting with Wrapper version 3.7.0, per-platform configuration of the backend communication mode is also possible using the following properties:

wrapper.backend.windows.type
Compatibility :3.7.0
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSX (Not Supported)Linux (Not Supported)Alpine Linux (Not Supported)FreeBSD (Not Supported)Solaris (Not Supported)IBM z/Linux (Not Supported)

List of possible values:

  • AUTO: use PIPE and in case of error, fallback to SOCKET
  • PIPE: use a pipe backend
  • SOCKET: use SOCKET_IPv4 and in case of error, fallback to SOCKET_IPv6
  • SOCKET_IPv4: use a IPv4 socket
  • SOCKET_IPv6: use a IPv6 socket

Defaults to the value of the wrapper.backend.type property.

Example: 
wrapper.backend.windows.type=PIPE

wrapper.backend.unix.type
Compatibility :3.7.0
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :Windows (Not Supported)Mac OSXLinuxAlpine LinuxFreeBSDSolarisIBM z/Linux

List of possible values:

  • AUTO: use PIPE and in case of error, fallback to SOCKET
  • PIPE: use a pipe backend
  • SOCKET: use the following modes in order of priority: SOCKET_PAIR (Unix only), with fallback to SOCKET_IPv4 and then to SOCKET_IPv6
  • SOCKET_PAIR (Since ver. 3.7.0): use a Unix domain socket pair
  • SOCKET_IPv4: use a IPv4 socket
  • SOCKET_IPv6: use a IPv6 socket

Defaults to the value of the wrapper.backend.type property.

Example: 
wrapper.backend.unix.type=SOCKET_PAIR

Reference: Port
  • wrapper.backend.type (3.5.8)

    Configures the communication between the Wrapper's process and the class running within the JVM.

  • wrapper.port (1.0.0)

    Configures the port that the Wrapper will use to connect to the JVM.

  • wrapper.port.max (3.2.0)

    Specifies the upper limit of the port range that the Wrapper will use to connect to the JVM.

  • wrapper.port.min (3.2.0)

    Specifies the lower limit of the port range that the Wrapper will use to connect to the JVM.

  • wrapper.jvm.port (3.2.0)

    Configures the port that the JVM will use to connect back to the Wrapper.

  • wrapper.jvm.port.max (3.2.0)

    Specifies the upper limit of the port range that the JVM will use to connect back to the Wrapper.

  • wrapper.jvm.port.min (3.2.0)

    Specifies the lower limit of the port range that the JVM will use to connect back to the Wrapper.