According to this wiki , You should NOT turn this option on in production. Engineer Engineer 3, 5 5 gold badges 26 26 silver badges 48 48 bronze badges. I dont think it's a good idea to modify a JSP page directly in production anyway; but still, this is good to know. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.
Visit chat. Linked If not specified, the default value of the flag is false. This will impact startup time of applications, but could prove to be useful on platforms or configurations where file locking can occur. If not specified, the default value is false. If true, Tomcat will prevent any file locking. This will significantly impact startup time of applications, but allows full webapp hot deploy and undeploy on platforms or configurations where file locking can occur.
Please note that setting this to true has some side effects, including the disabling of JSP reloading in a running server: see Bugzilla Please note that setting this flag to true in applications that are outside the appBase for the Host the webapps directory by default will cause the application to be deleted on Tomcat shutdown.
Maximum size of the static resource cache in kilobytes. If not specified, the default value is 10 megabytes. Amount of time in milliseconds between cache entries revalidation.
If not specified, the default value is 5 seconds. If the value of this flag is true , the cache for static resources will be used. If not specified, the default value of the flag is true. If the value of this flag is false , all case sensitivity checks will be disabled. Whether the context should process TLDs on startup. The default is true. The false setting is intended for special cases that know in advance TLDs are not part of the webapp.
If the value of this flag is true , the bytes output to System. If you turn this flag on, you should probably also turn tldValidation on. The default value for this flag is false , and setting it to true will incur a performance penalty. Amount of ms that the container will wait for servlets to unload.
If not specified, the default value of the flag is ms. If true, Tomcat will unpack all compressed web applications before running them. If not specified, the default value is true.
Pathname to a scratch directory to be provided by this Context for temporary read-write use by servlets within the associated web application. This directory will be made visible to servlets in the web application by a servlet context attribute of type java.
File named javax. You can nest at most one instance of the following utility components by nesting a corresponding element inside your Context element:. A context is associated with the org. Note that the brackets are actually part of the name, don't omit them. When you run a web server, one of the output files normally generated is an access log , which generates one line of information for each request processed by the server, in a standard format.
Catalina includes an optional Valve implementation that can create access logs in the same standard format created by web servers, or in any number of custom formats. You can ask Catalina to create an access log for all requests processed by an Engine , Host , or Context by nesting a Valve element like this:. See Access Log Valve for more information on the configuration attributes that are supported. If you use the standard Context implementation, the following configuration steps occur automtically when Catalina is started, or whenever this web application is reloaded.
No special configuration is required to enable this feature. For example, you can create an initialization parameter like this:. By default, overrides are allowed. The parameter value that will be presented to the application when requested by calling ServletContext. For example, you can create an environment entry like this:. However, it should be noted that RFC , section 8. In this case this attribute will need to be set to false to disable this feature. The default value for this attribute is false.
Set to false if Tomcat should not read any additional request body data for aborted uploads and instead abort the client connection. This setting is used in the following situations:. Not reading the additional data will free the request processing thread more quickly. Unfortunately most HTTP clients will not read the response if they can not write the full request. Note if an error occurs during the request processing that triggers a 5xx response, any unread request data will always be ignored and the client connection will be closed once the error response has been written.
If the value of this flag is true , the bytes output to System. If not specified, the default value of the flag is false. Setting this attribute to true will incur a performance penalty. Should the HttpOnly flag be set on session cookies to prevent client side script from accessing the session ID? Defaults to true. Controls whether HTTP 1. HttpServletResponse sendRedirect String will use relative or absolute redirects. Relative redirects are more efficient but may not work with reverse proxies that change the context path.
It should be noted that it is not recommended to use a reverse proxy to change the context path because of the multiple issues it creates.
Absolute redirects should work with reverse proxies that change the context path but may cause issues with the org. When a client provides the ID for a new session, this attribute controls whether that ID is validated. The only use case for using a client provided session ID is to have a common session ID across multiple web applications.
Therefore, any client provided session ID should already exist in another web application. If this check is enabled, the client provided session ID will only be used if the session ID exists in at least one other web application for the current host. Note that the following additional tests are always applied, irrespective of this setting:. Java class name of the org. Wrapper implementation class that will be used for servlets managed by this Context.
If not specified, a standard default value will be used. If the value of this flag is true , the parsing of web. If not specified, the default value of true will be used. Note also that if you turn this flag on, you should probably also turn xmlValidation on.
The standard implementation of Context is org. It supports the following additional attributes in addition to the common attributes listed above :. This only applies to web applications with a major version of 3 or higher.
Since this is a proprietary extension to the Servlet 3 specification, it is disabled by default. To enable this feature, set the attribute to true. This attribute provides a list of external locations from which to load resources for this context.
A resource will be searched for in the first docBaseN for which aliasPathN is a leading path segment of the resource. If there is no such alias, then the resource will be searched in the usual way. A more powerful feature for development only is Virtual webapp. If the value of this flag is true , symlinks will be allowed inside the web application, pointing to resources inside or outside the web application base path.
This will impact startup time of applications, but could prove to be useful on platforms or configurations where file locking can occur. If not specified, the default value is false. If true, Tomcat will prevent any file locking. This will significantly impact startup time of applications, but allows full webapp hot deploy and undeploy on platforms or configurations where file locking can occur.
Please note that setting this to true has some side effects, including the disabling of JSP reloading in a running server: see Bugzilla Please note that setting this flag to true in applications that are outside the appBase for the Host the webapps directory by default will cause the application to be deleted on Tomcat shutdown.
Maximum size of the static resource cache in kilobytes. If not specified, the default value is 10 megabytes. Maximum size of the static resource that will be placed in the cache. If not specified, the default value is kilobytes. Amount of time in milliseconds between cache entries revalidation. If not specified, the default value is 5 seconds. If the value of this flag is true , the cache for static resources will be used.
If not specified, the default value of the flag is true. If true and an sun. HttpClient keep-alive timer thread has been started by this web application and is still running, Tomcat will change the context class loader for that thread from the current WebappClassLoader to WebappClassLoader parent to prevent a memory leak.
Note that the keep-alive timer thread will stop on its own once the keep-alives all expire however, on a busy system that might not happen for some time. If true , when the web application is stopped Tomcat looks for SoftReference s to classes loaded by the web application in the ObjectStreamClass class used for serialization and clears any SoftReference s it finds.
This feature uses reflection to identify the SoftReference s and therefore requires that the command line option -XaddExports:java. This feature uses reflection to identify the leaks and therefore requires that the command line option -XaddExports:java. Applications without memory leaks should operate correctly with this attribute set to false. If true , Tomcat attempts to null out any static or final fields from loaded classes when a web application is stopped as a work around for apparent garbage collection bugs and application coding errors.
There have been some issues reported with log4j when this is true. Applications without memory leaks using recent JVMs should operate correctly with this attribute set to false. If true , Tomcat attempts to terminate threads that have been started by the web application.
Stopping threads is performed via the deprecated for good reason Thread. As such, enabling this should be viewed as an option of last resort in a development environment and is not recommended in a production environment. If this feature is enabled, web applications may take up to two seconds longer to stop as executor threads are given up to two seconds to stop gracefully before Thread.
If true , Tomcat attempts to terminate java. Timer threads that have been started by the web application. Unlike standard threads, timer threads can be stopped safely although there may still be side-effects for the application. If true , Tomcat attempts to clear java.
ThreadLocal variables that have been populated with classes loaded by the web application. On subsequent starts, the copied context XML descriptor will be used in preference to any context XML descriptor embedded inside the application even if the descriptor embedded inside the application is more recent.
The flag's value defaults to false. Note if the deployXML attribute of the owning Host is false or if the copyXML attribute of the owning Host is true , this attribute will have no effect. If true , any attempt by an application to modify the provided JNDI context with a call to bind , unbind , createSubContext , destroySubContext or close will trigger a javax. This exception can be disabled by setting this attribute to false in which case any calls to modify the JNDI context will return without making any changes and methods that return values will return null.
Created by Former user Deleted. Last updated: Jun 01, by Former user Deleted Version comment. Developers with slow machines be warned This will significantly impact the startup time of tomcat. Important things to know You should NOT turn this option on in production.
0コメント