Use this page to configure the web container settings.
To view this administrative console page, click
.Specifies a virtual host that enables a single host machine to resemble multiple host machines. Resources associated with one virtual host cannot share data with resources associated with another virtual host, even if the virtual hosts share the same physical machine.
Select a virtual host option:
Specifies that if a servlet is started once and it generates output to be cached, a cache entry is created containing not only the output, but also side effects of the invocation. These side effects can include calls to other servlets or JavaServer Pages (JSP) files, as well as metadata about the entry, including timeout and entry priority information.
Portlet fragment caching requires that servlet caching is enabled. Therefore, enabling portlet fragment caching automatically enables servlet caching. Disabling servlet caching automatically disables portlet fragment caching.
Specifies to disable the pooling of servlet request and servlet response objects that are pooled by the web container. When you disable pooling of servlet request and servlet response objects, new servlet request and servlet response objects are created for each request.
When you disable pooling of servlet request and servlet response objects, new servlet request and servlet response objects are created for each request, which can negatively affect performance, but provides protection from any unforeseen pooling bugs.
Specifies the number of threads that are available to handle asynchronous servlet timeout operations per server.
The default of two might be too low if you have many applications using asynchronous servlets that often have timeouts.
Specifies the default asynchronous servlet timeout for the server.
The default of 30 seconds can be lowered if responses are not being received quickly enough and there is a viable fall back in the error case. You can raise the value if too many timeouts are being received and the longer timeout produces responses in an acceptable manner to the client. The units are in millisecond, so multiply the number by 1000 to convert to seconds. To configure at a higher granularity, you must use the AsyncContext setTimeout method programmatically.
Select this option to use the same thread pool where the request originates. This option does not propagate any context from the original request.
Select this option to use an Asynchronous Beans work manager to start the runnable. This option is the default selection. The work manager option propagates any context that is configured for the selected work manager. This option also requires selecting the JNDI name of the work manager that you will use.