I've been reading through the archives and I've seen a lot of questions about using mod_webapp. In general, mod_webapp seems to be working pretty well for me. My problem is that it doesn't seem to be able to make a connection when httpd is started at boot time.
I'm using RedHat 7.0 and I've written init.d scripts for both Tomcat 4.0.1 and Apache 1.3.19 (both installed manually rather than from RPMs). Tomcat starts before Apache (Tomcat is S80 and Apache is S89). Both seem to be starting correctly and both can be accessed directly from their respective ports. The problem is that the Apache error_log has a string of entries like this... [Thu Feb 7 10:20:24 2002] [error] Connection "conn" cannot connect [Thu Feb 7 10:20:24 2002] [error] Cannot open connection "conn" ... and when I try to access a jsp from one of the contexts defined by WebAppDeploy in Apache, I get a "WebApp: Error 404 (File: wa_request.c Line: 198) Web-application not yet deployed" page, and an entry in the log like this one... [Thu Feb 7 10:20:42 2002] [error] Web-application not yet deployed Interestingly, viewing the source of this error page gives me the html that should be produced by the jsp application I was trying to access!! Restarting my web server seems to correct this problem. The connection is made and my jsp files are accessible as I would expect. This indicates to me that my configuration is essentially correct, but something is preventing the connection from being made at boot time. Could Tomcat not be fully loaded when Apache is trying to start? Should I put more space between the init.d scripts? Are there other daemons that need to be started in order for webapp to deploy? Any suggestions would be greatly appreciated. Cindy By the way, mod_webapp is version 1.0.1 built from source with -DEAPI. -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
