Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 27535 invoked from network); 2 Sep 2002 20:25:48 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Sep 2002 20:25:48 -0000 Received: (qmail 29843 invoked by uid 97); 2 Sep 2002 20:26:07 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 29795 invoked by uid 97); 2 Sep 2002 20:26:06 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 29783 invoked by uid 98); 2 Sep 2002 20:26:06 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Mon, 2 Sep 2002 21:25:27 +0100 (BST) From: Jocelyn Paine To: Tomcat Users List Subject: Re: Tomcat 4.0.4 under Windows NT crashes: "memory cannot be read" In-Reply-To: <5.1.0.14.2.20020901191608.02a75f38@pop3.cris.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Randall, I installed the 1.3.1 JSDK in place of 1.2, and this error _seems_ to have gone away. Since it wasn't 100% repeatable, I can't be sure, and will have to test it on my colleague's machine (which always tended to manifest the fault more often), but I may be lucky. You suggested I install JSDK 1.3.1 or 1.4.0: I wasn't able to install the latter, because InstallShield crashed "Interface not found" when it started the install proper, after unpacking its files. Surely Sun can't have left such an obvious bug, but perhaps they don't support NT 4 any more? In answer to your question, I'd been running Tomcat stand-alone, not glued to Apache. Finally, with reference to a comment in your earlier mail, is Tomcat indeed 100% Java? I.e. it doesn't include any native code? If so, I wonder what it was provoking to crash the 1.2 JVM (assuming that is indeed what happened) - nothing I've run has ever managed that before, not even the same application under a different server. (Since the fault appeared on two different machines, with different hardware configurations and Windows versions, I'd been assuming it was unlikely to be hardware or drivers.) Anyway, thanks for the advice. My colleague's machine is in France until next week, but when I can get at it, I'll post again if upgrading his JVM doesn't fix the problem. Jocelyn Paine http://www.ifs.org.uk/~popx/ +44 (0)7768 534 091 On Sun, 1 Sep 2002, Randall R Schulz wrote: > Jocelyn, > > I didn't read enough or carefully enough. > > > You really ought to get a more up-to-date version of the JRE or SDK. I > recommend 1.4.0_01 or 1.3.1, but using 1.2 at this point is not a good idea. > > > By the way, how do you (or your colleague) you get Tomcat to run as a > service? Via Apache? > > Are you certain that it's the Tomcat process that's crashing? Your > diagnostic didn't include the application name that is (I believe) in the > window title of the alert whose contents you reported. Is it "java.exe" or > something else? > > > Randall Schulz > Mountain View, CA USA > > > At 23:59 2002-08-31, you wrote: > >.... > > > >My system: Tomcat 4.0.4 is running stand-alone on Windows NT 4 (service > >pack 3); starting it by invoking Tomcat's startup.bat from a DOS window. > >My Java is Sun's "Classic VM (build JDK-1.2-V, native threads)". Machine > >is a 64 MB Dell Latitude. > > > >My colleague's system is a new Sony Vaio running Windows XP, same version > >of Tomcat, also a Sun JVM but probably a slightly newer one. Tomcat > >running as a service... > > > >Jocelyn Paine > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: