You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2015/11/07 09:27:10 UTC
[jira] [Comment Edited] (FELIX-5094) Make Jetty thread pool,
acceptors and selectors configurable
[ https://issues.apache.org/jira/browse/FELIX-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995120#comment-14995120 ]
Alexander Klimetschek edited comment on FELIX-5094 at 11/7/15 8:26 AM:
-----------------------------------------------------------------------
Attached patch: [^FELIX-5094.patch]
Will also print the actual configuration (that in the case of the defaults using -1 will be based on the number of cores for at least the acceptors) in the "Started Jetty" log line.
was (Author: alexander.klimetschek):
Attached patch: [^FELIX-5094.patch]
> Make Jetty thread pool, acceptors and selectors configurable
> ------------------------------------------------------------
>
> Key: FELIX-5094
> URL: https://issues.apache.org/jira/browse/FELIX-5094
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Alexander Klimetschek
> Attachments: FELIX-5094.patch
>
>
> Currently the jetty http service bundle does not expose configuration for Jetty's maximum thread pool size, number of acceptor and number of selector threads. It always uses Jetty's defaults.
> For tuning production machines these can be important settings that should be available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)