Apache Tomcat/4.0.1 - HTTP Status 404

[burs]

Hi there,

Whenever I want to access a servlet or static content via Jboss I get the error message: Apache Tomcat/4.0.1 - HTTP Status 404

I deployed the Tomcat sample application (copy webapps/ROOT to /jboss/deploy/handle). This standard app contains the org.apache.catalina.servlets.DefaultServlet for static content.

When I type http://localhost:8080/handle in the browser the URL changes to http://localhost:8080/handle/index.html indicating that the the welcome file was found.

But instead of the index.html a 404 error is displayed (The requested resource (/handle/index.html) is not available) Following message is in the console:

[INFO,EmbeddedCatalinaServiceSX] default: DefaultServlet.serveResource: Serving resource '/' headers and data

Does anyone has an idea what is wrong? Any comments are welcome.

Kind regard, sascha bur

mailto: [e-mail]

[adrian.brock]

I think you might have to rename the directory
to handle.war?

Regards,
Adrian

[cfs1]

I've had a stupid message on the examples file where if I searched for examples it didn't work but it started working for examples/

try it? You'll also need to have the file named yourfile.war or whatever...the .war will tell jboss to unpack and deploy your application.

-cs

[burs]

Hi there,

Thanks for the .war hint. It works now. Before I thougt that I must be the most stupid user. The simple solution proved that this is true ;-)

[mkent]

I've just starting playing with this as well. Is there something more that needs to be done than to copy a folder named "yourfile.war" to the deploy folder? It worked once for me to deploy files, but now it's now working to deploy the app, even after I restart JBoss/Tomcat.

[adrian.brock]

Which OS/verions?

Windows won't let you overwrite a deployed directory
structure because of the hard locking.

JBoss3 doesn't yet have support for directory based wars/ears.

Even with those two comments, a restart should work?

Regards,
Adrian

[mkent]

Actually, I realized after posting that there are other things the deployed folder needs (web.xml namely) to be "seen" properly. I've read the Error 500 Message thread and will try that out this weekend.

[mkent]

Oh, and I'm using Win NT4 on my laptop for the "testing" phase and Linux 7.2 on the app servers.