You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Keith Lea <ke...@cs.oswego.edu> on 2001/10/18 04:38:25 UTC

404's for webapps (and the WebAppInfo) on Apache even though Tomcat 4 works, mod_webapp-eapi loads fine, and WebAppDeploy is called

has anyone had similar problems? sigh. I don't get any errors loading the
precompiled mod_webapp-1.0-eapi module, and I follow all the directions for
enabling webapps on my virtual host.. LoadModule, AddModule, WebAppConnection,
WebAppDeploy. And the webapp I'm deploying does exist. And tomcat (4.0) is up
and 127.0.0.1:8008 connects to its warp thing. And port 8080 works fine for
http. And I've restarted apache, and tomcat. And yet even my WebAppInfo dir gets
a 404. So does my WebAppDeployed webapp. Can anyone help?

-kl

Re: Is JAR necessary after running?

Posted by Jim Cheesman <jc...@msl.es>.
At 04:52 AM 18/10/01, you wrote:
>     Hi all,
>
>     If Tomcat is startup already,
>     Can I delete servlet.jar?


Quick answer: try!
Real answer, at least on Win2000: no. Unless you're actually using a 
different servlet.jar to the one you think you are.

How to fake a delete on Win2000: overwrite the jar with another one, this 
time empty.


Jim


--

                           *   Jim Cheesman   *
             Trabajo: 
jchees@msl.es - (34)(91) 724 9200 x 2360
                           Evil is 
not all bad.

Is JAR necessary after running?

Posted by Sam <is...@ms45.hinet.net>.
    Hi all,

    If Tomcat is startup already,
    Can I delete servlet.jar?

    thanks.

Re: 404's for webapps (and the WebAppInfo) on Apache even though Tomcat 4 works, mod_webapp-eapi loads fine, and WebAppDeploy is called

Posted by Pier Fumagalli <pi...@betaversion.org>.
Keith Lea at keith@cs.oswego.edu wrote:

> has anyone had similar problems? sigh. I don't get any errors loading the
> precompiled mod_webapp-1.0-eapi module, and I follow all the directions for
> enabling webapps on my virtual host.. LoadModule, AddModule, WebAppConnection,
> WebAppDeploy. And the webapp I'm deploying does exist. And tomcat (4.0) is up
> and 127.0.0.1:8008 connects to its warp thing. And port 8080 works fine for
> http. And I've restarted apache, and tomcat. And yet even my WebAppInfo dir
> gets
> a 404. So does my WebAppDeployed webapp. Can anyone help?

If WebAppInfo gets 404 you _ARE_ in trouble... There's something wrong in
your httpd.conf... Send it over :)

    Pier