...
Parameter Name | Description | Requried | Possible Values | Default Value |
---|---|---|---|---|
http.proxyHost | If the outgoing messages should be sent through an HTTP proxy server, use this parameter to specify the target proxy. | No | A host name or an IP address |
|
http.proxyPort | The port through which the target proxy accepts HTTP traffic. | No | A positive integer less than 65535 |
|
http.nonProxyHosts | The list of hosts to which the HTTP traffic should be sent directly without going through the proxy. | No | A list of host names or IP addresses separated by '|' |
|
non-blocking | Setting this parameter to true is vital for reliable messaging and a number of other scenarios to work properly. | Yes | true |
|
HTTP PassThrough transport
HTTP PassThrough Transport is the default, non-blocking HTTP transport implementation based on HTTP Core NIO and is specially designed for streaming messages. It is similar to the old message relay transport, but it does not care about the content type and simply streams all received messages through. It also has a simpler and cleaner model for forwarding messages back and forth. It can be used as an alternative to the NHTTP transport.
The HTTP PassThrough Transport is enabled by default. If you want to use the NHTTP transport instead, uncomment the relevant NHTTP transport entries in axis2.xml
and comment out the HTTP PassThrough transport entries. The PassThrough Transport does not require the binary relay builder and expanding formatter.
Excerpt | ||
---|---|---|
Connection throttlingWith the HTTP PassThrough and HTTP NIO transports, you can enable connection throttling to restrict the number of simultaneous open connections. To enable connection throttling, edit the This will restrict simultaneous open incoming connections to 2. To disable throttling, delete the
|