Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 19653 invoked from network); 21 Jan 2002 22:44:09 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Jan 2002 22:44:09 -0000 Received: (qmail 1170 invoked by uid 97); 21 Jan 2002 22:44:06 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 1154 invoked by uid 97); 21 Jan 2002 22:44:06 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 1143 invoked from network); 21 Jan 2002 22:44:05 -0000 X-Originating-IP: [206.51.26.100] From: "Ed Milic" To: tomcat-dev@jakarta.apache.org Bcc: Subject: RE: jdk1.3.1 and tomcat 3.3a core dumping? Date: Mon, 21 Jan 2002 17:44:05 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 21 Jan 2002 22:44:05.0237 (UTC) FILETIME=[21379250:01C1A2CD] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Here is a solution that seems to work: You will need to edit how tomcat starts so that it uses the server JVM. CHANGE: if [ "$JAVACMD" = "" ] ; then # it may be defined in env - including flags!! JAVACMD=$JAVA_HOME/bin/java fi TO: if [ "$JAVACMD" = "" ] ; then # it may be defined in env - including flags!! JAVACMD=$JAVA_HOME/bin/java -server fi That should stop the crashing problems. >From: Dan Diodati >Reply-To: "Tomcat Developers List" >To: 'Tomcat Developers List' >Subject: RE: jdk1.3.1 and tomcat 3.3a core dumping? >Date: Mon, 21 Jan 2002 13:40:19 -0800 > > >I don't think the java code has any issues because it has been in >production >with jdk1.2.2 and tomcat 3.2.4. > >I tried using tomcat 3.2.4 and jdk 1.3.1_02 it this issue does NOT occur, >making me suspicious of >tomcat 3.3a. All the required patches for Solaris have been installed. >Anyone else know >of any incompatibilities with jdk1.3.1_02(the latest release of jdk131) and >tomcat 3.3a? > > >-----Original Message----- >From: Bojan Smojver [mailto:bojan@binarix.com] >Sent: Monday, January 21, 2002 1:30 PM >To: Tomcat Developers List >Subject: Re: jdk1.3.1 and tomcat 3.3a core dumping? > > >Even if you have buggy Java classes, this should not cause a good JVM to > do this. The problem is with the JVM. I'd try a different JDK, >something like 1.3.0_04 or maybe a newer sub-release of 1.3.1. > >Bojan > >PS. Keep in mind that I don't work with Solaris :-) > >Dan Diodati wrote: > > > I am having some problems with jdk1.3.1 core dumping with tomcat 3.3a. > > > > My current set up is apache 1.3.22 which is passing a the request > > to tomcat 3.3a(running externally). This is all running on a Solaris 8 >box > > (Sun Ultra2) using jdk1.3.1. > > When tomcat tries to compile some jsp pages, the Hotspot compiler core >dumps > > killing the JVM. Here is the error: > > > > # > > # HotSpot Virtual Machine Error, Internal Error > > # Please report this error at > > # http://java.sun.com/cgi-bin/bugreport.cgi > > # > > # Error ID: 47454E45524154452F4F502D41500E435050084B 01 > > # > > # Problematic Thread: prio=5 tid=0x31d1b8 nid=0x26 runnable > > # > > > > Has anyone else had any issues with jdk1.3.1 and tomcat 3.3a ? > > > > > > Dan > > > > -- > > To unsubscribe, e-mail: > > > For additional commands, e-mail: > > > > > > >-- >To unsubscribe, e-mail: > >For additional commands, e-mail: > > >-- >To unsubscribe, e-mail: > >For additional commands, e-mail: > > _________________________________________________________________ Join the world�s largest e-mail service with MSN Hotmail. http://www.hotmail.com -- To unsubscribe, e-mail: For additional commands, e-mail: