Re: 404 error on Tomcat 4.1.27...

2003-09-02 Thread Luciano Kiniti Issoe
We had the same problem here, in our case it was a NoSuchMethodException
generated when we compiled the code in JBuilder using some strange flags.
To debug this info, you must tail your localhost_log.2003-XX-XX.txt file
under the $TOMCAT_HOME/logs/
If you find the error but yet have no idea about what's going on, send us
the trace.

Regards,

miagi

- Original Message - 
From: "Darryl L. Pierce" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 02, 2003 4: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]



Re: 404 error on Tomcat 4.1.27...

2003-09-02 Thread Holger Klawitter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Tuesday 02 September 2003 21:46 schrieb Darryl L. Pierce:
> [...]I *always* get a 404
> error. 

In your webapp, do you rely on the invoker Serlvet to be enabled?
See the web.xml in $TOMCAT_HOME/conf.

Mit freundlichem Gruß / With kind regards
Holger Klawitter
- --
lists  klawitter  de
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iQIXAwUBP1T/5YeO6/fAymJdFAIyrAf+Lab/pftv8sOB2SBRYVuyre1Ht7Soxri8
gHONhS6ljd6bnSpBzwThCI8evJ217pQNHn8O66ZCcBsqoEARyFk9mMMhxALMzaQy
dVlVBJNEdSci0/OT9slzRdLh2OJuY9P1lUQ3sIIRpuo6MT5Gu3uVEOUu1GAxsa3N
5bPhbtQmSCckb/52p5vG4n4rcdinf3bpRH6h7Yrjnj57Pm9L585uzSjdddSAm9RI
Gzjo4RXHCWwxPDQj9Pkr4zPVbEgZKVLulZHPtH5IEt4xBJrOC1FLv1fjjIhr6+BT
NtJrqpZvYfvxbyeHlIUNPXQpnqO3i64bECgeUlS4aprMlZkq9nseyAf9Huld6L4H
BqRHn03YghJucMuVS8jcVSTAzF8W+u+DCzLyJTUQkSpxCWzTOykloMvLTyRdgZVS
nNJpOhZSDjcIDki6sV+D0ibhpjicR59p6WqDS4EVvtj3bCGGt94JHzH7dzm4Rcxt
Utyn97W469kuQXnC5lkJku5jhIOzEumvL7PYWwqJmfEDZ+vYTNWb+uaaEuQHWow1
xsJW+zBjzmYhyofviWGoGLdguqAJrqgzdAx+jiUgZ5ARdAdaykDIOqLVR/01M7NL
yB9P63smQMy2qvKVveDya5lRkCmixDBxKAVbsdZnG+fVjs93m+XcBYAA7Kds8GMB
pQ9iNc6ene35YQ==
=Ufh/
-END PGP SIGNATURE-


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: 404 error on Tomcat 4.1.27...

2003-09-02 Thread John Turner
What's the difference between your production environment and your laptop?

Symlinks enabled?  Invoker enabled?  Etc.

John

Darryl L. Pierce wrote:

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.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: 404 error on Tomcat 4.1.27...

2003-09-02 Thread Filip Hanik
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]



404 error on Tomcat 4.1.27...

2003-09-02 Thread Darryl L. Pierce
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 - 
"What do you care what other people think, Mr. Feynman?"


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]