This may seem long but I wanted to include anything I thought was relevant.
CATALINA_HOME=/usr/local/jakarta/jakarta-tomcat-4.0.2-b2 JAVA_HOME=/usr/java/jdk1.3.1_02 I added a new <Host> entry to server.xml for my new website. This is the only change I made to the stock server.xml. > <Host name="192.168.0.52" debug="0" appBase="webapps" unpackWARs="true"> > <Realm className="org.apache.catalina.realm.MemoryRealm" /> > > <Valve className="org.apache.catalina.valves.AccessLogValve" > directory="logs" prefix="192.168.0.52_access_log." suffix=".txt" > pattern="common"/> > > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="192.168.0.52_log." suffix=".txt" timestamp="true"/> > > <Context path="/manager" docBase="manager" debug="0" privileged="true"/> > > <Context path="" docBase="NewWebsite" debug="0" reloadable="true"> > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="NewWebsite_log." suffix=".txt" timestamp="true"/> > </Context> > </Host> This works great. When I point my browser at http://192.168.0.52:8080/ I get my home page and the JSP/servlet stuff works as expected. Like so many other, the next step is to set up the Warp connector so that I can front Tomcat with Apache. I changed the stock httpd.conf (RedHat 7.2 i386) by adding a new <VirtualHost> section to correspond to NewWebsite above. I installed mod_webapp.so from the downloaded webapp-module-1.0.2-tc402 archive. > NameVirtualHost 192.168.0.52 > > LoadModule webapp_module modules/mod_webapp.so > WebAppConnection warpConnection warp 192.168.0.52:8008 > WebAppDeploy examples warpConnection /examples/ > > <VirtualHost 192.168.0.52> > ServerName 192.168.0.52 > WebAppDeploy NewWebsite warpConnection / > </VirtualHost> The address 192.168.0.52 will eventually become a properly DNS-registered name www.NewWebsite.com (names and ip addresses may have been changed to protect the guilty). The intention is to have any request for http://192.168.0.52/ be redirected by mod_webapp to the NewWebsite Tomcat context. But that is not what happens. Instead, the browser sits as if it is loading something that never comes and there are no messages in any of the apache & tomcat log files on the server. Not even an access log entry. On startup of httpd I get the following message in the httpd error log. > [Thu Jan 31 12:49:58 2002] [warn] Loaded DSO modules/mod_webapp.so uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) > [Thu Jan 31 12:49:59 2002] [notice] Apache/1.3.20 (Unix) (Red-Hat/Linux) mod_python/2.7.6 Python/1.5.2 mod_ssl/2.8.4 OpenSSL/0.9.6b DAV/1.0.2 PHP/4.0.6 mod_perl/1.24_01 mod_throttle/3.1.2 configured -- resuming normal operations > [Thu Jan 31 12:49:59 2002] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) > [Thu Jan 31 12:53:08 2002] [error] Connection "warpConnection" cannot connect > [Thu Jan 31 12:53:08 2002] [error] Cannot open connection "warpConnection" > [Thu Jan 31 12:53:08 2002] [error] Connection "warpConnection" cannot connect > [Thu Jan 31 12:53:08 2002] [error] Cannot open connection "warpConnection" > [Thu Jan 31 12:53:08 2002] [error] Connection "warpConnection" cannot connect > [Thu Jan 31 12:53:08 2002] [error] Cannot open connection "warpConnection" > [Thu Jan 31 12:53:08 2002] [error] Connection "warpConnection" cannot connect > [Thu Jan 31 12:53:08 2002] [error] Cannot open connection "warpConnection" > [Thu Jan 31 12:53:08 2002] [error] Connection "warpConnection" cannot connect > [Thu Jan 31 12:53:08 2002] [error] Cannot open connection "warpConnection" > [Thu Jan 31 12:53:08 2002] [error] Connection "warpConnection" cannot connect > [Thu Jan 31 12:53:08 2002] [error] Cannot open connection "warpConnection" > [Thu Jan 31 12:53:08 2002] [error] Connection "warpConnection" cannot connect > [Thu Jan 31 12:53:08 2002] [error] Cannot open connection "warpConnection" > [Thu Jan 31 12:53:08 2002] [error] Connection "warpConnection" cannot connect > [Thu Jan 31 12:53:08 2002] [error] Cannot open connection "warpConnection" > [Thu Jan 31 12:53:08 2002] [error] [client 192.168.0.15] File does not exist: /var/www/html/NewContext > [Thu Jan 31 12:54:38 2002] [error] [client 192.168.0.15] File does not exist: /var/www/html/NewContext/ So I should probably first address the [warn] about EAPI. I've got jakarta-tomcat-connectors-4.0.2-b2-src.tar.gz and jakarta-tomcat-connectors-4.0.2-b2.patch from tomcat4-4.0.2-b2.1.src.rpm (though I can't remember where I got that src rpm?). I've unpacked it and am about to dive in but I thought I'd check with the group here to see if I'm going along the right track. Should the above configuration work (once I get rid of the EAPI problem with my freshly compiled mod_webapp.so)? One of the strange things (to me) is the setup I've shown here is the actual production machine that I'm trying to prepare. My development/test machine OS/Apache is very similar (RedHat 7.1 instead) and a very similar setup works fine. Thanks Kevin. __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
