From: Brian Munroe [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat not starting properly.
The CLASSPATH environment variable should never be used when running
Tomcat. (For that matter, it shouldn't be used in any Java
environment these days.)
Chuck: I don't mean to hijack this
On 8/29/07, Caldarale, Charles R [EMAIL PROTECTED] wrote:
The biggest problem with CLASSPATH is that it tends to be set and then
forgotten, causing classloading problems during subsequent Java
executions. The resulting confusion (especially if it involves the
wrong version of a class,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
Brian Munroe wrote:
I was always told that Tomcat ignored the CLASSPATH and
not to use it. Maybe that is one of those white lies they tell
newbies to alleviate problems? :)
The CLASSPATH environment variable is certainly not ignored by
On 8/29/07, Christopher Schultz [EMAIL PROTECTED] wrote:
The CLASSPATH environment variable is certainly not ignored by Tomcat.
Here's part of the startup script from TC 5.5:
# Add on extra jar files to CLASSPATH
if [ -n $JSSE_HOME ]; then
Hi chris,
are you sure about this CLASSPATH-thing?
a few lines above your quoted line catalina.sh sources/includes
setclasspath.sh which zaps CLASSPATH (First clear out the user classpath)
I just remembered it because i had to comment this line CLASSPATH=
to use my externally set environment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus,
Markus Schiegl wrote:
are you sure about this CLASSPATH-thing?
a few lines above your quoted line catalina.sh sources/includes
setclasspath.sh which zaps CLASSPATH (First clear out the user classpath)
Oh, hey, you're right. Thats what I
