geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trygve Sanne Hardersen (JIRA)" <>
Subject [jira] Commented: (GERONIMO-5668) Use fewer acceptor threads for Jetty
Date Mon, 01 Nov 2010 16:21:25 GMT


Trygve Sanne Hardersen commented on GERONIMO-5668:

>From the history it seems that Jetty 7.x releases are made approximately every 14 days.
7.2.0 was released on October 20th, and I can't find any open bugs targeting 7.2.x, but I
have no idea when a new release will be made.

Downgrading from 7.2.1-SNAPSHOT to 7.2.0 is trivial now, but I'm also maintaining a local
Geronimo version against Jetty 7.2.1-SNAPSHOT, and can provide a new patch when 7.2.1 is released,
be it before or after Geronimo 2.2.1 ships.

> Use fewer acceptor threads for Jetty
> ------------------------------------
>                 Key: GERONIMO-5668
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Jetty
>    Affects Versions: 2.2.1
>         Environment: Only tested on OS X 1.6 with Java 1.6
>            Reporter: Trygve Sanne Hardersen
>         Attachments: geronimo-2.2-1027647-jetty-acceptors.patch, geronimo-2.2-1028765-jetty-trunk.patch
> Geronimo applies the maxThreads parameter as the number of acceptor threads in Jetty,
with a default value of 50. With newer versions (7.2.0) of Jetty this gives the following
warning during startup:
> # Acceptors should be <=2*availableProcessors
> Server shutdowns are also very slow, it takes about 1 second to stop each acceptor thread.
> The attached patch sets the number of acceptor threads to 2 per connector (HTTP, HTTPS
and AJP), and exposes this and the acceptor queue size (50) as a parameter in

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message