Tomcat connectivity restrictions

Abstract: tomcat connectivity restrictions

</ Td> </ tr> <tr> <td width="417" height="35" valign="top" class="ArticleTeitle">
In the past few days the number of on-line systems are more than ever, with a few increases, a servlet can not return to normal data errors, users can create normal landing, and found dead on the server what abnormal. That the initial allocation of individual computers, although sometimes can not explain the phenomenon sometimes not, did not make serious consideration. Today the customer more and more must be done to seriously consider, although very busy, but also have to confront this issue to get it. Consider a system of written procedures for worse, that is certainly what improper handling procedures, and the crazy part of the relevant inspection procedures, which is not any other problem. I do not know what we should do at the time, whether the problem is suddenly the connection configuration tomcat from smaller?

Server.xml was opened, linking the allocation of places to find the original part of the connector maxProcessors only 75, really is a small, modify preserve and reopen.

Port = "80" minProcessors = "50" maxProcessors = "250"
EnableLookups = "true" redirectPort = "8443"
AcceptCount = "250" debug = "0" connectionTimeout = "20000"
UseURIValidationHack = "false" />
</ Td> <td width="267" align="center" valign="top" class="ArticleTeitle">
</ Td> </ tr> <tr> <td height="25" colspan="2" valign="top" class="ArticleTeitle">

â†‘ Back

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.