Larry,
I tried it- it did not work. I could not even get the
log file:
In tomcat 3.2 and tomact 3.3 I set the logging- but it
does not write to the log
<Logger name="tc_log" path="logs/tomcat.log"
verbosityLevel = "DEBUG"
/>
In 3.2 I get this error trying to run tomcat:
FATAL: configuration error
java.lang.SecurityException: sealing violation
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:234)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at
java.security.AccessController.doPrivileged(Native
Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:297)
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
javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:92)
at
org.apache.tomcat.util.xml.XmlMapper.readXml(XmlMapper.java:210)
at
org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:187)
at
org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235)
On 3.3 I can not grab the error.
My system classpath is:
CLASSPATH=.;c:\jdk1.3\lib\rt.jar;c:\xerces\xerces.jar;
c:\soap\lib\soap.jar;c:\wstk\uddi4j\lib\uddi4j.jar;
c:\wstk\wsdl4j\lib\wsdl4j.jar;c:\wstk\lib\wstk.jar;
c:\wstk\lib\xss4j.jar; c:\wstk\soap\lib\mail.jar;
c:\wstk\soap\lib\activation.jar;c:\webservices\classes;
c:\jsse\lib\jcert.jar; c:\jsse\lib\jnet.jar;
c:\jsse\lib\jsse.jar;c:\axis\lib\axis.jar;c:\axis\lib\log4j-gump.jar;
I have not made any change the tomcat.bat file in 3.2
or 3.3.
When I try the same thing on my win2000 machine
everything works great. There seems to be somethng
funky with win98.
TIA
Sanjay
--- Larry Isaacs <[EMAIL PROTECTED]> wrote:
> Is the tomcat.bat unmodified?
>
> Note that in its unmodified state, it contains:
>
> set CLASSPATH=%TOMCAT_INSTALL%\lib\tomcat.jar
>
> which replaces any CLASSPATH setting in your
> environment
> (your CLASSPATH setting is saved and restored
> however).
> The recommended procedure for adding classes to
> Tomcat 3.3
> is documented at:
>
>
<http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.html#configuring_classes>
>
> The stacktrace isn't complete and doesn't show the
> error. In server.xml, you can add:
>
> path="logs/tomcat.log"
>
> to the
>
> <LogSetter name="tc_log" ... />
>
> entry to capture Tomcat's log output in a file.
> Hopefully
> the stack trace will appear in the tomcat.log file.
>
> Cheers,
> Larry
>
> > -----Original Message-----
> > From: Sanjay bahal [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, November 28, 2001 12:01 AM
> > To: Tomcat Users List
> > Subject: RE: CLASSPATH for web apps - and the
> answer is?
> >
> >
> > Larry,
> > I am on win98, jdk1.3, Tomcat3.3. I have my
> > TOMCAT_HOME and JAVA_HOME setup.
> > My st\ystem classpath is:
> >
>
CLASSPATH=.;c:\jdk1.3\lib\rt.jar;c:\xerces\xerces.jar;
> >
> c:\soap\lib\soap.jar;c:\wstk\uddi4j\lib\uddi4j.jar;
> >
>
c:\wstk\wsdl4j\lib\wsdl4j.jar;c:\wstk\lib\wstk.jar;c:\w
> >
>
stk\lib\xss4j.jar;c:\wstk\soap\lib\mail.jar;c:\wstk\soap\lib\a
> > ctivation.jar;c:\webservices\classes;
> >
>
c:\jsse\lib\jcert.jar;c:\jsse\lib\jnet.jar;c:\jsse\lib\jsse.ja
> > r;c:\axis\lib\axis.jar;
> > Note: I removed jaxp, parser, crimso.jar from the
> > classpath.
> > I run tomcat c:\>tomcat run
> > The error I get is: [this is the best I can grab
> from
> > the DOS window]-
> >
> > at
> >
>
org.apache.tomcat.util.compat.Jdk12Support.doPrivileged(Unknown
> > Source)
> > at
> >
>
org.apache.tomcat.startup.EmbededTomcat.execute(Unknown
> > Source)
> > at java.lang.reflect.Method.invoke(Native
> > Method)
> > at
> >
>
org.apache.tomcat.util.IntrospectionUtils.execute(Unknown
> > Source)
> > at
> > org.apache.tomcat.startup.Main.execute(Unknown
> Source)
> > at
> org.apache.tomcat.startup.Main.main(Unknown
> > Source)
> > Guessed home=C:\tomcat
> > java.lang.reflect.InvocationTargetException:
> > org.apache.tomcat.core.TomcatExcept
> > ion: EmbededTomcat.initContextManager
> > at
> >
>
org.apache.tomcat.startup.EmbededTomcat.initContextManager(Unknown
> > Source)
> > at
> >
>
org.apache.tomcat.startup.EmbededTomcat.execute1(Unknown
> > Source)
> > at
> >
>
org.apache.tomcat.startup.EmbededTomcat$1.run(Unknown
> > Source)
> > at
> >
>
org.apache.tomcat.util.compat.Jdk12Support$PrivilegedProxy.run(Unknown
> > Source)
> > at
> > java.security.AccessController.doPrivileged(Native
> > Method)
> > at
> >
>
org.apache.tomcat.util.compat.Jdk12Support.doPrivileged(Unknown
> > Source)
> > at
> >
>
org.apache.tomcat.startup.EmbededTomcat.execute(Unknown
> > Source)
> > at java.lang.reflect.Method.invoke(Native
> > Method)
> > at
> >
>
org.apache.tomcat.util.IntrospectionUtils.execute(Unknown
> > Source)
> > at
> > org.apache.tomcat.startup.Main.execute(Unknown
> Source)
> > at
> org.apache.tomcat.startup.Main.main(Unknown
> > Source)
> >
> > Thanks a lot,
> > Sanjay
> > --- Larry Isaacs <[EMAIL PROTECTED]> wrote:
> > > I can't claim to be up to date with the latest
> state
> > > of Xerces, Xalan, and Jaxp, so there may be new
> > > issues
> > > that I'm not aware of with respect to
> combinations
> > > of Xerces, Xalan, etc.
> > >
> > > The fundamental problem in Tomcat 3.2.x is that:
> > >
> > > 1) The web server classes, including Jasper,
> live on
> > > the CLASSPATH.
> > >
> > > 2) I believe it is Jasper that requires an XML
> > > parser,
> > > so an XML parser has to exist on the
> CLASSPATH
> > > too.
> > >
> > > 3) Because Tomcat 3.2 uses the Java 2 sequence
> of
> > > classloader searching (as does Tomcat 3.3),
> > > classes
> > > found on the CLASSPATH take precedence over
> > > classes
> > > local to the web applications. Thus, all web
> > > applications are forced to use the XML parser
> on
> > > the
> > > CLASSPATH.
> > >
> > > Jasper doesn't care which XML parser. So you
> can
> > > upgrade the Jaxp 1.0.1 version (jaxp.jar +
> > > parser.jar)
> > > to crimson.jar (the current version has the
> jaxp.jar
> > > classes included) or xerces.jar depending on
> your
> > > other requirements. However, if you have two
> web
> > > applications that want different versions of XML
> > > parser,
> > > you are stuck.
> > >
> > > Tomcat 3.3 avoids forcing a single XML parser on
> all
> > > the web applications by building a more
> complicated
> > > classloader hierarchy which hides most of the
> server
> > > and Jasper classes from the web applications. A
> > > side
> > > effect of this is that adding classes and jars
> is
> > > more
> > > complicated than simply adding them to the
> > > CLASSPATH.
> > > This is why the tomcat.sh/tomcat.bat script
> ignores
> > > your
> > > CLASSPATH setting since that is all too often
> the
> > > wrong place to add them.
> > >
> > > Adding classes for Tomcat 3.3 is documented
> here:
> > >
> > >
> >
>
<http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.htm
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
