qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6683) Jetty thread seemingly spins if many HTTP ports are defined on hosts with large numbers of core
Date Tue, 11 Aug 2015 11:38:47 GMT

    [ https://issues.apache.org/jira/browse/QPID-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681671#comment-14681671
] 

ASF subversion and git services commented on QPID-6683:
-------------------------------------------------------

Commit 1695267 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1695267 ]

QPID-6683: [Java Broker] Give HTTP management ports separate individually configurable thread
pools

* Acceptor threads no longer defaults to a value derived from the number of cores.

Work by Lorenz Quack <quack.lorenz@gmail.com> and Keith Wall <kwall@apache.org>

> Jetty thread seemingly spins if many HTTP ports are defined on hosts with large numbers
of core
> -----------------------------------------------------------------------------------------------
>
>                 Key: QPID-6683
>                 URL: https://issues.apache.org/jira/browse/QPID-6683
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.32
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>             Fix For: qpid-java-6.0
>
>
> If I configure many HTTP management ports on a box with a large number of cores (80),
I find that one of the two ports will be non-functional (produce a timeout in the browser/blank
page).  Turning on Jetty logs reveals a Jetty WARN during startup, during the attempt to configure
the second port:
> {noformat}
> 2015-08-07 10:30:21,963 WARN  [Broker-Config] (o.e.j.s.AbstractConnector) - insufficient
threads configured for @0.0.0.0:8080
> {noformat}
> then evidence of a spinning Jetty thread once the connect
> {noformat}
> 2015-08-07 11:35:32,737 DEBUG [HttpManagement-226 Selector2] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@37ca01b0 to stopped
HttpManagement{5<=0<=50/50,1000}
> 2015-08-07 11:35:32,737 DEBUG [HttpManagement-233 Selector9] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@2f34e66d to stopped
HttpManagement{5<=0<=50/50,1000}
> 2015-08-07 11:35:32,737 DEBUG [HttpManagement-228 Selector4] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@3a041651 to stopped
HttpManagement{5<=0<=50/50,1000}
> 2015-08-07 11:35:32,737 DEBUG [HttpManagement-229 Selector5] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@3a041651 to stopped
HttpManagement{5<=0<=50/50,1000}
> 2015-08-07 11:35:32,738 DEBUG [HttpManagement-230 Selector6] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@62553d98 to stopped
HttpManagement{5<=0<=50/50,1000}
> 2015-08-07 11:35:32,738 DEBUG [HttpManagement-225 Selector1] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@4a3ef897 to stopped
HttpManagement{5<=0<=50/50,1000}
> 2015-08-07 11:35:32,740 DEBUG [HttpManagement-232 Selector8] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@6c32a795 to stopped
HttpManagement{5<=0<=50/50,1000}
> 2015-08-07 11:35:32,742 DEBUG [HttpManagement-227 Selector3] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@71985eb1 to stopped
HttpManagement{5<=0<=50/50,1000}
> 2015-08-07 11:35:32,745 DEBUG [HttpManagement-231 Selector7] (o.e.j.u.t.QueuedThreadPool)
- Dispatched Idle-org.eclipse.jetty.io.nio.SelectorManager$SelectSet$1@4a70f0ba to stopped
HttpManagement{5<=0<=50/50,1000}
> {noformat}
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message