If you want to control the number of concurrently executing threads more carefully than the Web application, control the number of concurrently executing threads in the URL group.

If a business logic (servlets and JavaBeans) that takes long processing time is present in a Web application, almost all the concurrently executing threads in the Web application are used, and the processing of other business logics may be in waiting state. In such a case, by specifying the setting to control the number of concurrently executing threads in the URL group, you can execute the business logics of the Web application without affecting the other processing.

Note that the URL that you can control with the number of concurrently executing threads indicates the request URI defined in RFC 2616. The URL that can control the number of concurrently executing threads in URL group does not include the query characters of request URI. An example is shown below.

• HTTP requests that can be controlled: /webapp/index.html
• HTTP requests that cannot be controlled: http: //localhost/webapp/index.html?id=0001

For guidelines on setting the number of concurrently executing threads in the URL group, see 8.3.4 Controlling the number of concurrently executing threads in a Web application in the uCosminexus Application Server System Design Guide.