-
1. Re: tomcat 3.2.1/jboss 2.4.0
samplecode Sep 24, 2001 9:06 AM (in response to samplecode)When I try to start Tomcat on its own I get the errors below. It seems to be having problem locating org.jboss.tomcat.* classes which make me suspect that I might need to JBoss add jars to my classpath so that they are accessible to the tomcat startup process.
linux:/usr/java/jakarta/build/tomcat/bin # ERROR reading /usr/java/jakarta/build/tomcat/conf/server.xml
At Line 128 /Server/ContextManager/ContextInterceptor/ className=org.jboss.tomcat.ContextClassLoaderInterceptor
FATAL: configuration error
java.lang.ClassNotFoundException: org.jboss.tomcat.ContextClassLoaderInterceptor
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at org.apache.tomcat.util.xml.ObjectCreate.start(XmlMapper.java:577)
at org.apache.tomcat.util.xml.XmlMapper.matchStart(XmlMapper.java:384)
at org.apache.tomcat.util.xml.XmlMapper.startElement(XmlMapper.java:81)
at org.xml.sax.helpers.XMLReaderAdapter.startElement(XMLReaderAdapter.java:329)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1451)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1700)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1700)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
at org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:317)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:260)
at org.apache.tomcat.util.xml.XmlMapper.readXml(XmlMapper.java:214)
at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:187)
at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235) -
2. Re: tomcat 3.2.1/jboss 2.4.0
samplecode Sep 24, 2001 9:39 AM (in response to samplecode)I got tomcat running without jboss by adding tomcat-service.jar and jboss.jar to my classpath. I might write a different startup script for tomcat to use its own classpath as my classpath is getting just a little long now!
JBoss is still not starting tomcat because of a java.lang.NoClassDefFoundError: org/apache/tomcat/logging/Logger. I think all I need to do is add the appropriate jars/paths to the startup script classpath and maybe it will work! -
3. Re: tomcat 3.2.1/jboss 2.4.0
samplecode Sep 24, 2001 10:00 AM (in response to samplecode)I concatenated $TOMCAT_HOME to the $JBOSS_HOME variable set in the run.sh startup script. The startup process cannot see org/apache/tomcat/logging/Logger even though its right off $TOMCAT_HOME (not a jar file) along with the rest of the org/apache/tomcat classes.
What am I missing? -
4. Re: tomcat 3.2.1/jboss 2.4.0
samplecode Sep 25, 2001 7:39 AM (in response to samplecode)It seems that the jboss-tomcat howto documentation is out of date. I downloaded the JBoss-2.4.1a_Tomcat-3.2.3.zip and now everything seems to work just fine. It looks like all I left out was append $JAVA_HOME/lib/tools.jar to the JBOSS_PATH in run.sh