1

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?

Improve this question
4
  • What do the logs say? Commented Jun 22, 2011 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. Commented Jun 24, 2011 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. Commented Jun 24, 2011 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... Commented Jun 27, 2011 at 12:13

1 Answer 1

Reset to default
1

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.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.