Return-Path: 
 <tomcat-user-return-31075-qmlist-jakarta-archive-tomcat-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 83109 invoked from network); 27 Aug 2002 11:15:33 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 27 Aug 2002 11:15:33 -0000
Received: (qmail 11177 invoked by uid 97); 27 Aug 2002 11:14:36 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org
Received: (qmail 11083 invoked by uid 97); 27 Aug 2002 11:14:34 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 8789 invoked by uid 98); 27 Aug 2002 06:57:12 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Date: Tue, 27 Aug 2002 07:56:40 +0100 (BST)
From: Jocelyn Paine <popx@ifs.org.uk>
To: tomcat-user@jakarta.apache.org
Subject: Tomcat 4.0.4 under Windows NT crashes with system error: "memory
 cannot be read"
Message-ID: <Pine.LNX.4.21.0208270752430.15739-100000@pop3.ifs.org.uk>
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

I'm using Tomcat for Java and JSP in a large server-side application. My
Web browser is also running on this machine (a 64 MB Dell Latitude
laptop), using loopback to connect to the server. Most of this works fine.
However, in a few parts of the application, Tomcat crashes:  Application
Error. The instruction at "<memory address>" referenced memory at "<memory
address>". The memory cannot be read.

This error is semi-repeatable. It only shows up in some parts of the
application, but not every time, even though I take exactly the same path
through the application after starting Tomcat. Perhaps it shows up one
time in 5. The Java code itself is OK: it has run fine on the same machine
under New Atlanta's ServletExec servlet engine, and under various flavours
of Linux using the JRun servlet engine. (On one ISP, it has run for a year
and a half without any crashes.)

I've not been able to get any info about the error from Tomcat's logs, or
from the DOS window in which I started it.

The 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)". The
Windows version is probably not too important, since the same fault
happens under Windows XP.

The crash also happens on a colleague's system: a new Sony Vaio running
Windows XP, same version of Tomcat, also a Sun JVM but probably a slightly
newer one.

Ideas for circumvention? I'd like to use Tomcat, but dare not if it is
going to fail with this kind of random error. What puzzles me is this
semi-repeatability - why, if the fault is only provoked in specific parts
of the application, does it not happen every time?

Jocelyn Paine
http://www.ifs.org.uk/~popx/
+44 (0)7768 534 091 



--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>