-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shrikant,
On 12/8/2010 3:03 PM, shrikant patel wrote: > So threads and corresponding thread setting (like maxThreads, > acceptCounts etc) associated with connectors are shared between the 2 > apps. That means if the traffic increase for app1 and request for it > start to queue up, the app 2 request may suffer delay or time out. Correct. > Going through the documentation, it seems one way of resolving this > would be, to declare 2 separate services in service.xml for the 2 > apps. Correct: Connectors are associated with a Service, a Service has multiple Hosts and each host has any number of deployed webapps. In order to have connectors serve separate webapps exclusively, you actually have two options: 1. Two Services, separate Hosts, Connectors, and deployed webapps 2. Single Service, Host, and webapp with two Connectors: each connector must be on a different IP/port combination so you can have users of one webapp use a specific connector. You can enforce the use of a specific Connector by using a Valve or Filter to check the incoming port number and rejecting requests for the "wrong" webapp. > Each service will have its on http connector with appropriate > maxThread and acceptCount settings. That way high volume on app1 does > not starve or timeout the app2 requests. If you have other shared resources such as a database, you might still have one webapp affecting the other. Of course, you will be sharing memory and CPU time as well. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0AB9kACgkQ9CaO5/Lv0PDxUgCfQcmWa40Gh5FROWplOWGR8xr8 WxoAoKrJiFRrjeKVzRRs/XZohsL2aUSq =AZ8R -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
