explanation seems plausable. I'd be interested in knowing if
this is a known JVM bug or a Xerces bug?
Al
- Original Message -
From: pete [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, September 02, 2001 3:25 AM
Subject: Re: Segmentation Fault when modifying classpath?!
You're not by any
You're not by any chance using Suns JDK 1.3.1 and Linux are you?
If you are, add 'ulimit -s 2048' to tomcat.sh (or just type it in the
shell you launch tomcat from).
This limits the maximum stack size, but i can't give you more detail
than that, all i know is it works for me.
This problem
- Original Message -
From: pete [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, September 02, 2001 3:25 AM
Subject: Re: Segmentation Fault when modifying classpath?!
You're not by any chance using Suns JDK 1.3.1 and Linux are you?
If you are, add 'ulimit -s 2048' to tomcat.sh
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 03, 2001 12:06 AM
Subject: Re: Segmentation Fault when modifying classpath?!
Thanks Pete! I will give that a shot. I am using Sun's JDK1.3.1 under
Redhat 7.1 (sorry, forget to mention my setup!).
I did, however, run across a post detailing
!
-Original Message-
From: simon [mailto:[EMAIL PROTECTED]]
Sent: Sunday, September 02, 2001 5:23 PM
To: [EMAIL PROTECTED]
Subject: Re: Segmentation Fault when modifying classpath?!
Hello Al,
If you set the environment variable TOMCAT_OPTS to -classic you are not
actually setting a tomcat option
Ok...
All this surrounds modifying tomcat.sh per install instructions found in
apache-soap.
Per Apache-Soap's Getting Tomcat Ready, I have changed my classpath to put
xerces.jar at the beginning of my classpath as follows:
unset CLASSPATH
CLASSPATH=/usr/local/java/lib/xerces.jar
for i in
