Implement an auto-reload feature by editing the context.xml file. Locate the following lines and change the listings value from false to true: Directory browsing helps when testing the system, and sometimes it may be the solution for a 403 forbidden error. To enable directory browsing, locate the web.xml file in the conf directory and edit the file with a text editor. To choose a different port, edit the server.xml file with a text editor, such as Notepad++, and locate the following lines: Ĭhange the connector port number to any number between 105.ĥ. If you have any problems with the header size, add a maxHttpHeaderSize = "65536" to increase enlarge from the default maximum of 8K to 64K.Important: Back up the. In some cases this may be insufficient, particularly when larger data on the HTTP header are transmitted. If not specified, this attribute is set to 8192 (8 KB). The Tomcat connector attribute maxHttpHeaderSize defines the maximum size of the request and response HTTP header, specified in bytes. Please contact your database admin to find out which number of connections is acceptable for your database. This can be done by changing the value of the properties and in iteraplan/WEB-INF/classes/iteraplan-db.properties. It is strongly recommended though, that the maximum number of database connections is updated accordingly, such that it is always higher than the maximum number of threads. If, for some reason, your Tomcat needs to be able to handle requests on these ports in more threads, we still recommend that you configure it as described above, but change the value of the maxThreads attribute to a more appropriate value. The standard configuration for iteraplan's database connection pool is 21, to ensure that there is always at least one more database connection available and to avoid this problem. Such a situation may occur when there are more threads writing concurrently to the database than database connections are available.
The purpose of this is to avoid a possible deadlock in one of the database access libraries used by iteraplan. This causes all requests to be handled by tomcat with a maximum of 20 threads. Please note that, while the settings for these connectors may vary depending on your personal system's configuration, the executor attribute has to be set and the connectors themselves must not specify any of the attributes maxThreads or minSpareThreads to avoid conflicts. In order to do this, the $TOMCAT_HOME/conf/server.xml has to be modified.įirst, you have to define an Executor with the name iteraplanThreadPool within the Service Catalina (after the line ), if it does not already exist. If the Tomcat on which iteraplan is deployed is not expected to run under heavy load and/or iteraplan is the only application deployed on it, we recommend you to limit the number of Tomcat threads that process requests to 20. Limit Maximum Number of Request-processing Threads Should you experience such problems, please contact the iteraplan support in order to find a solution. Under rare circumstances, this setting might break character encoding of non-English characters in other applications on that Tomcat instance. Please be aware that this option applies to all applications which are deployed on your Tomcat. Be sure to add the attribute to all of them.
Typically, there are between one and three active connectors configured in Tomcat.
0 kommentar(er)
