PassThrough Transport is a non-blocking HTTP transport implementation based on HTTP Core NIO, and is the default HTTP transport shipped with the ESB Profile of WSO2 Enterprise Integrator (WSO2 EI). Although the PassThrough Transport is somewhat similar to the NHTTP transport, it overcomes all the limitations of the NHTTP transport and provides a significant performance gain. The PassThrough Transport also has a simpler and cleaner model for forwarding messages back and forth.
...
Code Block |
---|
<transportReceiver name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLListener"> ... <parameter name="CertificateRevocationVerifier">true< enable="true"> <CacheSize>1024</CacheSize> <CacheDelay>1000</CacheDelay> </parameter> </transportReceiver> |
...
Code Block |
---|
<transportSender name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLSender"> ... <parameter name="CertificateRevocationVerifier">true<" enable="true"> <CacheSize>1024</CacheSize> <CacheDelay>1000</CacheDelay> </parameter> </transportSender> |
...
Excerpt | ||
---|---|---|
Connection throttlingWith the PassThrough transport and HTTP NIO transport, 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
|
Configuring Listeners
The PassThrough transport has 4 HTTP/HTTPS listneres by default. It includes 2 PassThroughHttpListener
threads and 2 PassThroughHttpSSLListener
threads.
You can configure the number of listeners in the <EI_HOME>/conf/passthru-http.properties
file using the io_threads_per_reactor
property. You are able to define any number of listeners as there is no maximum limit defined in the code level.
Note |
---|
The number of listener threads is double the value of the For example, if you defined the value for the |