[
https://issues.apache.org/jira/browse/GERONIMO-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926906#action_12926906
]
Trygve Sanne Hardersen commented on GERONIMO-5668:
--------------------------------------------------
I have looked a bit more at this and have filed a bug for Jetty, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=329180. This is based on Shawn's
work, many thanks.
I'll watch the Jetty bug and let you know if it gets fixed at the Jetty side so
that Geronimo can be updated to use a newer Jetty version. I have a patch ready
for running Geronimo against Jetty trunk.
> 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.
