geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Jiang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-5668) Use fewer acceptor threads for Jetty
Date Thu, 28 Oct 2010 14:40:24 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925820#action_12925820
] 

Shawn Jiang commented on GERONIMO-5668:
---------------------------------------

Patch committed with 22@r1027647.    The closing speed increases remarkably with the patch.
 But it's still slower than before.

Let's see if the upgrade will cause any new tck failures before deciding to revert the upgrade.

> Use fewer acceptor threads for Jetty
> ------------------------------------
>
>                 Key: GERONIMO-5668
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5668
>             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 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 config-substitutions.properties.

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


Mime
View raw message