When you control the number of concurrently executing threads in the Web application, note the following points:

• When the number of threads exceeds the maximum number of concurrently executing threads in Web container
  Since only the requests equal to the minimum number of threads secured in the Web application are implemented when all of the following conditions are satisfied, the thread count may temporarily exceed the maximum number of concurrently executing threads in the Web container.
  
  • If the value set for the number of concurrently executing threads in the Web container is completely used when the access is centralized.
  • If a Web application in which the number of dedicated threads is set, is deployed
  • If a request arrives in the deployed Web application, before completion of the request processing threads that are running
• Access to be controlled
  Apart from the access to servlets and JSPs, the number of concurrently executing threads is also to be controlled when the static contents are accessed.
  
• Notes for using the error page customization functionality
  When using the error page customization functionality with <error-page> tag used in web.xml, the number of concurrently executing threads is not controlled in processing of the request that is transferred when an error occurs. There are no restrictions as a result of controlling the number of concurrently executing threads.
  
• About the threads
  The dedicated threads are not generated as exclusive threads of the Web application. The minimum number of threads secured when a Web application is executed is set here for the thread count.
  Note that the threads for request processing is re-used in the entire Web container.
  
• Maximum number of concurrently executing threads in Web application
  Even if a value greater than the maximum number of concurrently executing threads in Web container is set as the maximum number of concurrently executing threads in Web application, you can deploy the Web application on a J2EE server. Note that the maximum number of concurrently executing threads in Web container is, however used for the maximum number of concurrently executing threads in deployed Web application.
  
• When the number of shared threads in Web application is 0 or less
  If you deploy a following type of Web application, the number of shared threads in Web application may become 0 or less. Note that if the number of shared threads in the Web application is 0 or less, deployment of the Web application fails. You can consider the following cases in which the number of shared threads is 0 or less:
  
  • When a Web application with setting to control the number of concurrently executing threads in URL group is already deployed, and an attempt is made to deploy another Web application with the number of dedicated threads set
  • When the number of dedicated threads, and the setting to control the number of concurrently executing threads in URL group is specified in a Web application to be deployed, and the number of shared threads in Web application is already 0 or less during setup