You are viewing a plain text version of this content. The canonical link for it is here.

Posted to general@jakarta.apache.org by "Kevin A. Burton" <bu...@relativity.yi.org> on 2000/03/25 12:44:49 UTC

Re: Jetspeed 1.0 causing Seg fault in Tomcat on Redhat 6.1 - Anyideas?

jon * wrote:
> 
> on 3/24/00 11:48 AM, Jeff Haynes <Je...@techno.ca> wrote:
> 
> > SIGSEGV received at bddff7bc in unknown. Processing terminated
> > Writing stack trace to javacore27991.txt ... OK
> 
> This shouldn't happen EVER. If it does, it is a bug in your JVM, not Tomcat
> or Jetspeed. Either try a different JVM and/or send that javacore file to
> IBM's bug tracking so that they can fix it...

Yes.  It is the JVM.  The IBM JDK 1.1.8 (newest) with GLIBC 2.1 does
this.  No way to get around it.  If you run it under the SUN JDK 1.2
this doesn't happen.

The older JDK 1.1.8 (November?) didn't do this.

Kevin
-- 
Kevin A Burton (burton@apache.org)
http://relativity.yi.org
Message to SUN:  "Please Open Source Java!"
"For evil to win is for good men to do nothing."