On 03/20/2012 02:01 AM, Alex Samad - Yieldbroker wrote:
This has me thinking and think I have found another bug. :)Our setup is IIS 7.5 setup as a Reverse proxy. We run PRD, UAT through here. Trying to treat this an infrastructure box. We have 2 in a NLB setup For each environment I have a separate web server and directory setup so C:\ABC\ Prod\ Ajpconfig\ UAT\ Ajpconfig\ In each environment I have a ajpconfig directory where I put my dll and I keep all my config files for just that environment. The idea was that I could have different version of the tomcat connector thus test stuff out in UAT and then move on to PRD. BUT there is no way to set the name space used in the tomcat connector in relation to the Shared Memory or to semaphore. So Global\\JK_ISAPI_REDIRECT_MUTEX is used by all tomcat connectors (the ones in prod and the ones in UAT)
Yes, but thats used only inside jk_init and locks for 1ms during new worker process creation while the isapi_redirect gets loaded to memory. Like explained in BZ52659 you have things conceptually wrong. isapi_redirect is proxy, it does its own connection pool management, recycling, virtual host mapping handling etc. 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. You can eventually have two separate pools (one for testing and other for production)
And I would presume the Shared Memory would also be shared between the 2 ? Quote from the doco ! " The ISAPI redirector can read it's configuration from a properties file instead of the registry. This has the advantage that you can use multiple ISAPI redirectors with independent configurations on the same server. The redirector will check for the properties file during initialisation, and use it in preference to the registry if present."
If something is possible it doesn't mean you should use it in production and in all cases.
You can't do this with the IIS connector and with multiple processes (web gardens)!
Again, you should think 'differently' Entire IIS worker process recycling is meant for handling crappy .NET applications with memory and resource leaks. isapi_redirect is proxy, nothing else, nothing more. Regards -- ^TM --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
