Bug 702095 - Consider increasing default number of http client threads in RHQServer
Consider increasing default number of http client threads in RHQServer
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
All All
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
Blocks: rhq41 rhq41-ui
  Show dependency treegraph
Reported: 2011-05-04 14:35 EDT by Mike Foley
Modified: 2011-08-23 15:41 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-08-23 15:41:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
YSlow showing 91 HTTP requests to load a page (83.85 KB, image/png)
2011-05-04 14:35 EDT, Mike Foley
no flags Details
YourKit profiling showing only 15 HTTP Client threads in RHQ Server (74.09 KB, image/png)
2011-05-04 14:36 EDT, Mike Foley
no flags Details

  None (edit)
Description Mike Foley 2011-05-04 14:35:47 EDT
Created attachment 496877 [details]
YSlow showing 91 HTTP requests to load a page

Description of problem:
To load a typical page in RHQ4.0 page typically more than 90 seperate HTTP requests are being made (see attached image which documents this).  The RHQ 4.0 server has less than 15 HTTP client threads in the default configuration to handle this.  This is a performance constraint on page load.  Consider tweaking the default configuration of RHQ to increase the number of http client threads to remove this constraint.  

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.   Review pages with FF's YSlow plugin
2.   Review the number of HTTP client threads available with a profiling tool
Actual results:

Expected results:

Additional info:
2 attachments:  1) an image documenting > 90 HTTP requests per page.  2) an image documenting < 15 HTTP Client threads available in the default RHQ server
Comment 1 Mike Foley 2011-05-04 14:36:27 EDT
Created attachment 496878 [details]
YourKit profiling showing only 15 HTTP Client threads in RHQ Server
Comment 2 Ian Springer 2011-08-23 15:41:54 EDT
The maxThreads option for the RHQ Server's HTTP connector is configured in RHQ_SERVER_HOME/jbossas/server/default/deploy/jboss-web.deployer/server.xml and is templatized to use the value of the rhq.server.startup.web.max-connections property in RHQ_SERVER_HOME/bin/rhq-server.properties. rhq.server.startup.web.max-connections is set to 200 out of box, which is also the Tomcat default if the maxThreads option is not specified. 

Mike, the fact that there are 15 HTTP connector threads doesn't mean that's the maximum value; it just means that's all Tomcat needed to create to handle incoming requests. Note, another way to check the # of threads currently in the pool is to check the value of the Threads Allocated metric on Connector Resources in RHQ. 

When Tomcat runs out of HTTP connector threads, it logs a message similar to the following:

org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads (200) or check the servlet status

I have never seen this error, and I don't recall any users ever reporting the error, so I think we can keep the value at 200 for now. If we start getting reports of users hitting that error, we'll know what we need to do.

Note You need to log in before you can comment on or make changes to this bug.