On 7 Feb 2008, at 08:02, Asankha C. Perera wrote:
Currently I'm using the NIO transports on the client side as well,
and by default java uses http 1.1, which in turn uses keep alive
by default.
Is there any way to customize the NIO sender behavior?
Yes, by making a property file called "nhttp.properties" available
on the classpath. Look at the NHttpConfiguration class for more
details - However note that the defaults are very much cable of
handling huge loads
Ref: http://svn.apache.org/viewvc/synapse/trunk/java/modules/
transports/src/main/java/org/apache/synapse/transport/nhttp/
NHttpConfiguration.java?view=markup
I know how to change SO_TIMEOUT and so on,
You can change things like SO_TIMEOUT, CONNECTION_TIMEOUT,
SOCKET_BUFFER_SIZE, STALE_CONNECTION_CHECK, TCP_NODELAY etc Look at
HttpCoreNIOSender.getClientParameters() method
but how can I change -- for example -- the max number of requests
that are sent over the same channel (the tomcat NIO connector
allows such thing)?
You mean for re-using existing connections? if so there is no
limit, if a free channel is 'available' it will be used
Yes, I know about those parameters.
However the tomcat NIO connector can be customized in a greater way
[1], for example it allows to bound the maximum number of requests
that can be pipelined. Is there any way to achieve a similar result
with the synapse transport?
Michele
[1] http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
