You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/10/28 23:38:27 UTC
[jira] [Commented] (KNOX-611) Expose configuration for Jetty's
thread pool and connection queue
[ https://issues.apache.org/jira/browse/KNOX-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979394#comment-14979394 ]
ASF subversion and git services commented on KNOX-611:
------------------------------------------------------
Commit d98f8dd5fcd505073a361de97c135706bad2d343 in knox's branch refs/heads/master from [~kevin.minder]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=d98f8dd ]
KNOX-611: Expose configuration for Jetty's thread pool and connection queue
> Expose configuration for Jetty's thread pool and connection queue
> -----------------------------------------------------------------
>
> Key: KNOX-611
> URL: https://issues.apache.org/jira/browse/KNOX-611
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.7.0
> Reporter: Kevin Minder
> Fix For: 0.7.0
>
>
> Currently Knox uses Jetty's default thread pool and connection queue configuration. As of 8.1.14.v20131031 these are minThread=8, maxThread=254, maxQueue=-1. The maxQueue=1 implies and unlimited connection queue.
> The settings should be exposed as optional settings gateway-site.xml. The absence of these settings should fall back to the Jetty defaults.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)