Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] (Am I) using persistent connections with Jetty

If you use HTTP1.1 from the clients the connections will be persistent
by default. Even if the client does not close them, after some idle
timeout jetty can close them (see
http://wiki.eclipse.org/Jetty/Howto/Configure_Connectors description
of maxIdleTime and lowResourcesMaxIdleTime).

Jan

On 11 May 2012 06:14, Otis Gospodnetic <otis_gospodnetic@xxxxxxxxx> wrote:
> Hello,
>
> Would using Jetty (7? 8?) and persistent connections make sense in situations where clients more or less constantly stream data to the server?
>
> For example, imagine a system where client applications:
> * are running on hundreds of nodes of some cluster
> * are constantly collecting performance metrics
> * are sending these metrics via HTTP to some server
>
> Qs:
> * Would it make more sense to have clients keep persistent connections with the server instead of opening/closing them?
> * If I'm not explicitly closing HTTP connections on either client (using HttpClient lib) or server (servlet running in Jetty 7.*) side, am I effectively already keeping all connections open/persistent?
>
> Thanks,
> Otis
> ----
> Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users


Back to the top