From 9ed89fa692e35a45d5230da78d5e0fda1e370a55 Mon Sep 17 00:00:00 2001 From: "Maria Odea B. Ching" Date: Sun, 12 Jul 2009 02:16:53 +0000 Subject: [PATCH] [MRM-1214] submitted by: Igor Galic (jmcg) o added troubleshooting tips when deploying as war git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@793260 13f79535-47bb-0310-9956-ffa450edef68 --- archiva-docs/src/site/apt/adminguide/webapp.apt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/archiva-docs/src/site/apt/adminguide/webapp.apt b/archiva-docs/src/site/apt/adminguide/webapp.apt index d2242c537..fa908da11 100644 --- a/archiva-docs/src/site/apt/adminguide/webapp.apt +++ b/archiva-docs/src/site/apt/adminguide/webapp.apt @@ -82,3 +82,9 @@ Configuring and Running Archiva Once Archiva is running, it is configured in the same way as the standalone instance. See the {{{../quick-start.html#Setting%20up%20your%20Archiva%20instance} quick start}} guide for more information. +Troubleshooting + + One of the least decipherable errors you can get from Tomcat is a <<<404>>> when the deployment fails. In <<<\/logs/catalina.out>>> you will only find that it fails, but not why. Also Archiva's logs will not tell you. + + The log messages and stack traces in case of a <<<404>>> can be found in <<<\/logs/localhost.\>>>. + -- 2.39.5