Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 12997 invoked from network); 1 Mar 2001 11:04:12 -0000 Received: from mx1.decode.is (root@213.167.128.30) by h31.sny.collab.net with SMTP; 1 Mar 2001 11:04:12 -0000 Received: (from root@localhost) by mx1.decode.is (8.9.3/decode) id LAA10697 for tomcat-user@jakarta.apache.org; Thu, 1 Mar 2001 11:03:49 GMT Received: from smail.decode.is (smail.decode.is [172.18.0.18]) by mx1.decode.is (8.9.3/decode) with ESMTP id LAA10657 for ; Thu, 1 Mar 2001 11:03:48 GMT Subject: RE: Crashing tomcat MIME-Version: 1.0 Date: Thu, 1 Mar 2001 11:04:11 -0000 Content-Type: text/plain; charset="iso-8859-1" Message-ID: <56AA4E1C98A43E41A75C8643D4F0B724DE77@smail.decode.is> X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Crashing tomcat Thread-Index: AcCiPXXsv4Nj0ZoNQ06j11URqg1NaQAATOig From: =?iso-8859-1?Q?Stef=E1n_F=2E_Stef=E1nsson?= To: X-scanner: scanned by Inflex 0.1.5 - (http://www.inflex.co.za/) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mx1.decode.is id LAA10697 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hello.. Are you guys running windows? If so, are you getting the popup window with the red cross and an ok button saying that some memory address can't be read? If that is the case I would bet that you have found a bug in the JVM. The reason for that being that Java doesn't have any pointers so there is no way that any of your code could generate this message. Java would not allow you to write into an illegal memory address, this window would only appear if the JVM was doing something like that (or perhaps the JDBD driver, depending on what type of driver you are using). Are you guys using any native code (dll's or system calls)? What type of JDBC driver are you using (Type 4 is pure java and should therefore not be able to cause this behavior but Type 1 (and maybe Type 2 too) may rely on native code and could therefore cause the error message to occur. Hope this gives you guys a hint, Regards, Stefan. -----Original Message----- From: dick [mailto:dick@javacatz.com] Sent: 1. mars 2001 10:50 To: tomcat-user@jakarta.apache.org Subject: Re: Crashing tomcat Hi Christopher, I also use some taglib to query a database (mysql) and then show the result in html back. It occasionally crash, I don't know the reason too. So, let's figure the reason out ! Regards Dick Poon ----- Original Message ----- From: "Christopher Miller" To: Sent: Thursday, March 01, 2001 6:16 PM Subject: Crashing tomcat > I have written a simple servlet to access a database and place the > results in an html page. However this is regularly crashing the tomcat > server. > > I have tomcat and apache running together with the basic config files, > but I am not sure where the fault lies (servlet or config file). > > the error on tomcat crashing is in the form of > > "instruction at xxx referenced memory at xxx. the memory could not be > written" > > Any help would be well received. > > Chris > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, email: tomcat-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, email: tomcat-user-help@jakarta.apache.org