Thanks Dan for your reply. Your suggestion is very much appreciated. Running multiple instances as a workaround for this may be fine for a handful of virtual hosts, but if you have 50 or 100? How much memory and CPU or even how many physical machines do I need for that?
I would also find it error-prone having to administer multiple different ports. Currently adding and deleting a virtual host is a fully automated process. I have one jsp page on one host only and for the rest I have only 2 servlets for each host. The servlets generate remote scripts only - no jsp and no HTML at all. I also don't have any security issues on the server side because users cannot upload server-parsed documents. I can't imagine that running so many virtual machines and tomcats will serve me well. Currently this is handled beautifully with mod_jserv but feel I have to switch to tomcat because old mod_jserv doesn't appear to be supported with Apache httpd version 2. I just need a very basic robust, cooperative servlet engine for this and not a space shuttle solution. Am I perhaps using the wrong servlet engine? I could live without jsp entirely as long as the old <servlet> tag as a means of java server-side include is supported. Regards, Bernard On Thu, 17 Mar 2005 19:15:00 -0800, you wrote: >Not sure what your need or frequency is for routine adding/deleting of a >virtual host is, but have you considered running multiple instances of >Tomcat and connecting them each over different jk port? Perhaps, one >instance runs your stable virtual hosts - another runs your dynamic set of >virtual hosts? I have experienced that Tomcat tends to startup more slowly >the more virtual hosts you have in the config. I run with multiple >instances of Tomcat and when I do need to restart Tomcat, it is relatively >quick. Doesn't address your session issue though. > >btw I run FC2/Apache 2.0/JK2/Tomcat 5.0.28 > >At 05:33 PM 3/17/2005, Bernard wrote: >>Hi, >> >>I would like to hear opinions from users or developers who have a >>little more experience with mod-jk/Tomcat then me. >> >>With multiple virtual hosts, I would like to add and delete virtual >>hosts on a routine basis. >> >>This is achieved by re-starting both httpd and tomcat after >>re-configuration (I don't know any other way). >> >>Surprisingly, Apache immediately returns a server error 500 response >>while Tomcat is re-starting. >> >>IMHO this renders almost useless the init() and destroy() servlet >>logic that is used to make user sessions persistent before and after a >>server restart. >> >>If, for example, the expected servlet response is JavaScript that is >>embedded in a web page, then the whole web application gets broken >>without even showing an error by this. >> >>This is so because there is no way that I can catch this error in >>JavaScript. >> >>The error 500 response is HTML and and the script engine cannot read >>it. >> >>This is just a special case but I think an error 500 response for a >>server re-start could be considered a disaster in most other cases as >>well. >> >>What can be done about this? >> >>I have filed a bug: >>http://issues.apache.org/bugzilla/show_bug.cgi?id=34050 >> >>Do you agree with my view? >> >>How long would a thing like this take to fix? >> >>Many thanks, >> >>Bernard >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
