On 03/20/2012 06:55 AM, Alex Samad - Yieldbroker wrote:
You should 1. Create a separate 'Unmanaged' application pool for isapi_redirect 2. Disable recycling for that pool 3. Have multiple vhost mapping inside uriworkermap.properties instead having multiple configuration files and instances for each vhost. 4. Use a single process for that pool.Okay I can see that Our original thinking was if we separate prd and uat, they could not affect each other.
Sure that's probably the only reason to have multiple instances and pools. However this still does not require multiple worker processes or recycling.
:) true, but I don't believe the above is true on IIS/Windows. The think I am unsure on is how the connector uses the shared memory If its index (?) by the name of the worker thread or loadbalancer name then there will be a problem. I have the same config in UAT and PRD.. and thus the same worker names and load balancer names
You will need to have /jakarta inside different 'Site' and each site bound to its own AppPool. Shared memory is constructed from site name, so for example for 'Default Web Site' it becomes something like JK_LOCALHOST_1_... Suppose you have that separated already between production and staging. Regards -- ^TM --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
