Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 32986 invoked from network); 10 Dec 2002 22:38:52 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Dec 2002 22:38:52 -0000 Received: (qmail 28871 invoked by uid 97); 10 Dec 2002 22:39:46 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 28813 invoked by uid 97); 10 Dec 2002 22:39:45 -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 28799 invoked by uid 98); 10 Dec 2002 22:39:45 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.7.1 Date: Tue, 10 Dec 2002 16:38:19 -0600 From: "Aymeric Alibert" To: "<" Subject: TC 4.1 and VM crash: how to report issue? Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_3A66FCF5.7D1C5527" X-Guinevere: 2.0.8 ; X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --=_3A66FCF5.7D1C5527 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable We are running a Tomcat 4.0 server in our production environment and I am trying to upgrade to Tomcat 4.1. I ran some load test recently and was horrified to see the server crashing = even under moderate load. After more testing, I found that starting the VM with = the -server option systematically crash the VM after few minutes of load test. The server works fine even under heavy load with the -client option. The same behavior can be reproduced with both JDK1.4.0 and JDK1.4.1. My TC4.0 server runs fine with the -server option. Now, this is obviously a JVM problem but probably won't have any help = from=20 SUN since: - I cannot create a test case to reproduce my problem. - I works fine with TC4.1 Can someone help me with this issue or at least guide me to the right = contact? I found several tickets opened on the SUN bug database with similar issues = but none of them had a resolution or people assigned to work on them. Thanks! Aymeric --=_3A66FCF5.7D1C5527--