wrapper.backend.type

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

The Wrapper needs to maintain constant communication between the Wrapper process and a class running within the JVM. This communication has traditionally been done using a socket across the loopback device (localhost). This has been safe and reliable but some users have requested an alternative because of security or other issues.

The default value is "AUTO".

List of possible values:

  • AUTO: use SOCKET and in case of error, fallback to PIPE
  • 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
  • PIPE: use a pipe backend
Example:
wrapper.backend.type=SOCKET

WARNING

Along with other security improvements in version 3.6.0, PIPE mode, which previously used named pipes, has been changed to use anonymous pipes.

When using wrapper.backend.type=PIPE, transmitting sensitive data via the backend channel can pose a security risk. While older versions of the Wrapper generally do not use the backend to transmit sensitive data, this risk is more significant when using the wrapper.app.property.<n> properties introduced in version 3.5.57.

Upgrading to at least version 3.6.0 is recommended if you are using PIPE mode. See vulnerability #13 for more details.

Reference: Port