look in your log files, this usually means that the deployment of your context failed, and tomcat continued to start up
Filip ----- Original Message ----- From: "Darryl L. Pierce" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Tuesday, September 02, 2003 12:46 PM Subject: 404 error on Tomcat 4.1.27... My company has been using 4.0.6 for about a year now and we've recently upgraded to 4.1.27. On our production server, all works just fine: we can copy the WAR file into webapps, start Tomcat and all is well and good. However, on my development laptop, when I do the same thing with the same distribution, WAR file and configuration, I *always* get a 404 error. I checked inthe webapps directory and the servlet's context has been created (the WAR file is unpacked) and the class I'm trying to hit is there, but Tomcat is complaining that the resource is not available. This is also happening on a plain vanilla Tomcat installation. I unpacked the tarball, changed the server.xml to listen on the correct ports, and nothing, I get a 404 error. Any ideas? I'm running Debian GNU/Linux and am using J2SDK 1.4.1. -- Darryl L. Pierce <[EMAIL PROTECTED]> Visit the Infobahn Offramp - <http://bellsouthpwp.net/m/c/mcpierce> "What do you care what other people think, Mr. Feynman?" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
