To recap, I've got a situation where Tomcat is crashing on takeoff, on a
V5R4 AS/400, with what appears to be the same setup that works fine on a
V6 box, and showing correct environment variables in the STDOUT spool
file, and leaving this in Catalina.out.
java.lang.ClassNotFoundException: org.apache.catalina.startup.Catalina
at java.net.URLClassLoader.findClass(URLClassLoader.java:432)
at java.lang.ClassLoader.loadClass(ClassLoader.java:642)
at java.lang.ClassLoader.loadClass(ClassLoader.java:608)
at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:236)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
to which Rainer Jung replied:
. . .
All this works by default in an untampered Tomcat installation. It can
break:
- if catalina.jar is not in /wintouch/tomcat/lib or it is not readable
- if catalina.properties is not in /wintouch/tomcat/conf, or it is not
readable, or the entries for the server.loader or common.loader are broken
- the start scripts do not set -Dcatalina.base=/wintouch/tomcat/ and
-Dcatalina.home=/wintouch/tomcat/ when starting the JVM
- you are changing the place of the used properties file by giving a
non-default value in the system property -Dcatalina.config during startup.
I can find, so far, no evidence to indicate any of these possibilities.
But is there some diagnostic I could enable, that would allow me to find
out more detail about the problem? Or maybe something I could try from a
QShell command line in a terminal session?
--
James H. H. Lampert
Touchtone Corporation
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
