awarnier wrote: > > hepabolu wrote: > ... > >> However, from the Tomcat docs I understand that any change to server.xml >> requires a restart of Tomcat which would mean that the existing >> (non-dummy) >> hosts which are already in production, i.e. up and running, will also be >> taken offline. This is the heart of the problem... > > Just as another look on the issue. > > <skip/> > > This may be one case where the added complication of having an Apache > httpd in front of Tomcat is justified. >
I'm not sure if this will not result in unwanted side-effects. Each webapp should store/retrieve information from a MySQL database (one per host/client). There should be absolutely no possibility of a mix of information of clients. Each webapp serves as a webservice to an external webapp/webservice. They communicate using the predefined domainname. I don't think it's a good idea to have one webapp handle all requests based on parameters alone. There are already a lot of parameters to handle a single request, figuring out which 'client' should respond makes it all the more complicated. I could look into the 'multiple webapps in a single domain' setup. I just wonder if there's (a) extra processing time due to the apache + mod_jk configuration and (b) added complexity to figure out which webapp is the culprit in case of troubles. I'll take (b) for granted if (a) is almost nothing as I'm already having troubles with timeout deadlines. Do you have any info on processing times using apache + mod_jk? Thanks. Bye, Helma -- View this message in context: http://www.nabble.com/Virtual-host-configuration---best-practise--tp25512289p25530061.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
