tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "simon" <si...@lexues.co.jp>
Subject Re: Segmentation Fault when modifying classpath?!
Date Mon, 03 Sep 2001 00:22:37 GMT
Hello Al,

If you set the environment variable TOMCAT_OPTS to -classic you are not actually setting a
tomcat option but a JVM option.  This
means that you will no longer be using the 'hotspot' feature of the JVM, which will obviously
have an impact on performance.

I had all sorts of segfault problems using the Sun JVM 1.3.1 on Linux 7.1 and 6.2.  I trawled
through the Bug Parade on the javasoft
site.  Some of it got really technical and there were as many solutions as there were opinions.
 I tried most of them but the most
successful was switching to the IBM JVM.  The segfaults stopped and I am still getting the
performance benefit of a JIT compiler.
(I therefore concluded that it is a problem with the JVM - same as Pete below)

I'm sorry that this is just another 'it worked for me' but I hope it helps.

simon

----- Original Message -----
From: "Alejandro Calbazana" <acalbazana@rcn.com>
To: <tomcat-user@jakarta.apache.org>
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 a problem similar to mine.  The
> suggested solution was to set the TOMCAT_OPTS environment variable
> to -classic.  After setting this environment variable, everything ran
> nicely.  If anyone can give me any more detail on either solution, that
> would be great.  I hate to implement a fix but not know the root cause.
>
> Pete, your 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" <pete@claudia.dyn.dhs.org>
> To: <tomcat-user@jakarta.apache.org>
> 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 (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 only seems to show up with xerces, but since it works fine
> > on other JVMs, and on Sun JDK1.3.1 on Windows, i'd say Sun have a buggy
> > JVM here.
> >
> > IBM's JDK does not have this problem, so that may be another option for
> you.
> >
> > Hope that helps
> >
> > -Pete
> >
> > >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 ${TOMCAT_HOME}/lib/* ; do
> > >  if [ "$CLASSPATH" != "" ]; then
> > >    CLASSPATH=${CLASSPATH}:$i
> > >  else
> > >    CLASSPATH=$i
> > >  fi
> > >done
> > >...
> > >
> > >When starting tomcat I get the following:
> > >
> > >Using classpath:
> > >/usr/local/java/lib/xerces.jar:
> > >/opt/jakarta-tomcat-3.2.3/lib/activation.jar:
> > >/opt/jakarta-tomcat-3.2.3/lib/ant.jar:
> > >/opt/jakarta-tomcat-3.2.3/lib/jasper.jar:
> > >/opt/jakarta-tomcat-3.2.3/lib/LICENSE:
> > >/opt/jakarta-tomcat-3.2.3/lib/mail.jar:
> > >/opt/jakarta-tomcat-3.2.3/lib/servlet.jar:
> > >/opt/jakarta-tomcat-3.2.3/lib/soap.jar:
> > >/opt/jakarta-tomcat-3.2.3/lib/test:
> > >/opt/jakarta-tomcat-3.2.3/lib/webserver.jar:
> > >/opt/jakarta-tomcat-3.2.3/lib/xerces.jar:
> > >/usr/local/java/jdk1.3.1/lib/tools.jar
> > >
> > >/opt/jakarta-tomcat-3.2.3/bin/tomcat.sh: line 181: 12681 Segmentation
> fault
> > >$JAVACMD $TOMCAT_OPTS -Dtomcat.home=${TOMCAT_HOME}
> > >org.apache.tomcat.startup.Tomcat "$@"
> > >
> > >I can not figure out for the life of me why this is happening.  I've also
> > >tried setting the classpath from the shell with the exact same results.
> Any
> > >hints appreciated.
> > >
> > >Thanks,
> > >
> > >Al Calbazana
> > >
> >
> >
> >
> >
>
>


Mime
View raw message