[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

diff --git a/archiva-docs/src/site/apt/adminguide/webapp.apt b/archiva-docs/src/site/apt/adminguide/webapp.apt
index d2242c5377614d8cb8fd103774f107cdb43fe3ca..fa908da1145aad4707eaf2b7d070f1c02c9a248e 100644 (file)
--- 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 <<<\<tomcat home\>/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 <<<\<tomcat home\>/logs/localhost.\<date\>>>>.
+