axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty" <mgai...@hotmail.com>
Subject Re: [axis2] SimpleHTTPServer as transport listener causes too many connections to stay in TIME_WAIT state
Date Wed, 06 Feb 2008 20:58:56 GMT
with regards to the last question..
I would take a look at increasing the maxThreads parameter on the
NIOConnector e.g
  <Connector port="80" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150" connectionTimeout="60000" redirectPort="8443" />

M--
----- Original Message -----
From: "Michele Mazzucco" <Michele.Mazzucco@ncl.ac.uk>
To: <axis-user@ws.apache.org>
Sent: Wednesday, February 06, 2008 12:37 PM
Subject: Re: [axis2] SimpleHTTPServer as transport listener causes too many
connections to stay in TIME_WAIT state


>
> On 6 Feb 2008, at 16:50, Asankha C. Perera wrote:
>
> > Michele
> >
> >>> Not if you are using the NIO listener on the server side and
> >>> sending requests on the NIO listeners' port..
> >> No, calls were made to the tomcat port.
> > I don't understand what you are trying to achieve here.. if you are
> > using the o.a.synapse NIO based transports to get over the
> > TIME_WAIT problems with the Tomcat/Servlet transport, why do you
> > keep sending messages to the Tomcat port instead of the NIO ports?
>
> The synapse transports are used for outgoing messages.
>
>
> >>> No.. the NIO client / Sender is optimized for a server
> >>> environment - like Synapse - and thus not recommended for a
> >>> simple client, as it starts a NIO reactor and a thread pool for
> >>> handling IO requests with dedicated IO threads etc. So, this will
> >>> be good for your server side if you are making many outgoing
> >>> calls from the server side..
> >>>
> >> What about if the client is a load generator?
> > If you want a really good load generator for web service calls, use
> > the benchmark code from Apache HttpComponents - its as good as or
> > better than ApacheBench for web services
> > Code - http://svn.apache.org/repos/asf/httpcomponents/httpcore/
> > trunk/contrib/src/main/java/org/apache/http/contrib/benchmark/
> > Binary - https://www-lk.wso2.com/~asankha/benchmark/
> > Sample / Reference - http://wso2.org/library/1721
>
> Please correct me if I'm wrong, but it looks to me that your client
> is deterministic, i.e. does not introduce any randomness (for example
> for the arrival rate, I'd like an average value of x, but with some
> distribution, not via constant values) -- which is very important in
> real systems.
>
> >>> BTW.. I think you are developing something like an ESB??
> >> Something like that, but with some smart forwarding/throttling
> >> policies
> > Have you looked at Apache Synapse? It uses the above NIO transports
> > very effectively and is optimized for high performance. It supports
> > throttling, caching etc and a host of other features - even on
> > clustered HA environments
>
> Yes.
> >>>> No, the client is on a remote machine. I've tried to use both
> >>>> blocking
> >>>> and non blocking sender/listener on the client side, and the
> >>>> bottleneck
> >>>> seems to be the server.
> >>>>
> >>> This could very well be due to a weakness on the client side..
> >>> for example even if you used ApacheBench you will could bad
> >>> performance for some cases as it doesn't support HTTP 1.1!
> >>
> >> No, I've written the client, and it's pretty optimized.
> > Can you share a TCPDump of a sample request made by your client and
> > the response received.. in particular I am interested to know if
> > you use
> > 1. HTTP 1.1
> > 2. Keepalive connections
> > 3. Chunking
> >
> I've tried all the possible combinations.
> 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?
> I know how to change SO_TIMEOUT and so on, 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)?
>
> Michele
>
> > asankha
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Mime
View raw message