Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For deploying and troubleshooting an application, getting 404s has little use. I have deployed applications that report no issue in the logs but return 404s. There IS an error in the application as I've found it through some trial and error.

Is there a way to have Tomcat actually return the error it's encountering as opposed to the 404?

share|improve this question
What do the logs say? – Flimzy Jun 22 '11 at 5:33
They don't say anything. The server loaded up. The web app is present. I looked in the admin console, the web app is there. – Nick Swarr Jun 24 '11 at 19:14
The logs should always say something. I suspect you're not looking in the right place. If there really are no logs, then you must have them disabled. – Flimzy Jun 24 '11 at 19:18
The WAR being deployed was an incomplete archive. It was missing some files that caused the web app to not function. The logs didn't indicate anything was amiss (and maybe they wouldn't have in this case). Back to my original question... – Nick Swarr Jun 27 '11 at 12:13

If there is no servlet taking up this path, there is pretty little Tomcat can do to even know the "real" error.

If there is definitely a servlet assigned to the path that gives the 404 error, you should check this servlet. The JSF Facelets Servlet for example notoriously (and annoyingly) throws a 404 by default, if a page exists, but is missing an included file.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.