archiva-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r804899 - /archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt
Date Mon, 17 Aug 2009 08:35:34 GMT
Author: oching
Date: Mon Aug 17 08:35:34 2009
New Revision: 804899

[MRM-1085] CLONE -Failing to startup due to invalid bean definition
o updated documentation for setting appserver.base and appserver.home in Windows
o added more troubleshooting tips for startup errors


Modified: archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt
--- archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt (original)
+++ archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt Mon Aug 17 08:35:34 2009
@@ -54,14 +54,39 @@
    Bug 40668}} for a workaround.
    * The ${appserver.base} java property is used by the Archiva internal logging configuration
to determine where to output its logs to.
-     It is important to define this property either in the $CATALINA_OPTS system environment
variable (if Tomcat is being launched via the
+     It is important to define this property either in the $CATALINA_OPTS system environment
variable if Tomcat is being launched via the
      command line) or the service properties (if being launched as a service or daemon).
The format typically expected is
      -Dappserver.base=<SOMEWHERE>. In this example, we'll put the logs in Tomcat's
<<<logs>>> directory so we need to set appserver.base
      property to where Tomcat is installed:
-export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME"
+export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME" (for
+set CATALINA_OPTS="-Dappserver.home=%CATALINA_HOME% -Dappserver.base=%CATALINA_HOME%" (for
+   * If setting the ${appserver.base} and ${appserver.home} using the previous step does
not work, you can set it in the unpacked Archiva web application's
+     <<<WEB-INF/classes/>>> as follows:
+# for Windows:
+# or, for UNIX:
+   * When running Tomcat as a <<Windows>> service, you need to edit <<<regedit>>>
and then, in
+     <<<HKEY_LOCAL_MACHINE \> SOFTWARE \> Apache Software Foundation \>
Procrun 2.0 \> TomcatX \> Parameters \> Java>>>, modify
+     the <<<Options>>> variable. Set the ${appserver.base} property by
adding the following parameters at the end:
+-Dappserver.base=%CATALINA_HOME% -Dappserver.home=%CATALINA_HOME%
  For more information, see {{{}
Archiva on Tomcat}} in the wiki.
@@ -84,6 +109,40 @@
+* Error During Startup
+  There are cases when the Tomcat logs only shows the following error during startup:
+Aug 17, 2009 11:04:02 AM org.apache.catalina.core.StandardContext start
+SEVERE: Error listenerStart
+Aug 17, 2009 11:04:02 AM org.apache.catalina.core.StandardContext start
+SEVERE: Context [/archiva] startup failed due to previous errors
+Aug 17, 2009 11:04:04 AM org.apache.coyote.http11.Http11BaseProtocol start
+  One of the common causes for this <<<listenerStart Error>>> is a failure
during Spring's initialization. One way to diagnose or confirm the
+  exact cause of the error is by adding the following configuration to the unpacked Archiva
webapp's <<<WEB-INF/classes/log4j.xml>>>:
+<appender name="console" class="org.apache.log4j.ConsoleAppender">
+  <layout class="org.apache.log4j.PatternLayout">
+    <param name="ConversionPattern" value="%d [%t] %-5p %c %x - %m%n"/>
+  </layout>
+<logger name="org.springframework.web">
+  <level value="debug"/>
+  <appender-ref ref="console"/>
+   The above configuration directs Spring's output logs to the Tomcat console and be recorded
in Tomcat's log files. 
+* Diagnosing Errors
   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\>>>>.

View raw message