[
https://issues.apache.org/jira/browse/GERONIMO-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927022#action_12927022
]
Kevan Miller commented on GERONIMO-5668:
----------------------------------------
Nice.
Is there an outlook for Jetty 7.2.1 release? We're getting pretty close to a G
2.2.1 release, I think. Would be great to see this problem fixed in 2.2.1, but
would hate to see a Jetty release holding up the 2.2.1 release...
Trygve, many thanks for tracking this issue down!
> 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-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 config-substitutions.properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
