参考：http://wrapper.tanukisoftware.com/doc/english/prop-jvm-port.html
The Wrapper is able to use a socket to communicate with its Java component running inside a JVM. This property allows the configuration of the port that the JVM will use to connect back to the Wrapper.
Until Wrapper version 3.5.9, when a port of "0" (zero) is specified, the Wrapper will treat this as if the property has not been specified. Later versions than 3.5.9, however will let the JVM select any open and usable port. This is also the way the JVM-sided port was created until Wrapper version 3.1.2.
If the port specified by this property couldn't be bound because the port is already being used, or hasn't been specified, then the Wrapper will be using the range of wrapper.jvm.port.min - wrapper.jvm.port.max properties to bind a port.
If a specific port should be used, then any port in the range 1 - 65535 may be specified. Note that on UNIX systems port numbers below 1024 will most likely require root access to be set. If the specified port is in use, then the Wrapper will display a warning to the log and, as with the default case, will search for the first available port.
When the Wrapper launches a JVM instance, it will open a server socket listening on the port defined by thewrapper.port property. The JVM will then connect back to Wrapper, internally using the port specified by this property or the range subsequentially.
| Example: |
wrapper.jvm.port=0 |
Controlling the port range. |
||||||||
"wrapper.jvm.port.min" and "wrapper.jvm.port.max": In some cases, it is necessary to control the range of ports that the Wrapper will use when choosing a port. The defaults were chosen to make it very unlikely that they would conflict with any well-known ports numbers (from 0 to 1023 generally assigned on most systems). If the default 31000-31999 range is causing problems, it can be changed using the wrapper.jvm.port.min and wrapper.jvm.port.max properties. If these are used, be sure to provide a large enough range to make it unlikely that all of the ports will be in use when the Wrapper attempts to start.
|
背景：
同一台服务器上，客户安装了hana数据库和hybris应用，当新建一个hana数据库后，发现数据库无法正常启动，报错端口冲突。
修改：
hybris启动的参数文件：
/hybris5.5/hybris/bin/platform/tomcat/conf/wrapper.conf
添加了这几个参数：
wrapper.port.min=36000
wrapper.port.max=36999
wrapper.jvm.port.min=35000
wrapper.jvm.port.max=35999
重新启动。
