Thanks for your detailed response. See questions below.
In-process Tomcat is to have Tomcat running in the same process space as > Apache HTTPD, IIS, or other web server. Since most of the web servers > are implemented in C/C++, you will have to use JNI to integrate with > Java-based Tomcat, and create a "mod_tomcat" like module for Httpd. So there's no standard prepackaged installation of the two combined, or no standard "connector" plugin or something that's distributed with either Tomcat or HTTPD, which is why I'd have to create it myself? Is the in-process approach that uncommon? Definitely the in-process setup improves performance, since > communication between Tomcat and web server occurs via memory-based data > exchange. It will be less stable since if something went wrong with the > Tomcat, it would affect the web server directly. It will also be less > scalable, since this setup won't support high-availability and > clustering of Tomcat servers. Why does the in-process approach render high-availability and clustering impossible? From a technical/implementation perspective, what is it about the in-process approach that causes this specific functionality to not be possible? In any case, if clustering features don't work then it's definitely no surprise that any web application that needs to scale wouldn't use this approach...unless it is being used in some way by such web applications in production - anybody know? -- View this message in context: http://www.nabble.com/In-Process-Tomcat-tf3972772.html#a11281236 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
