Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 97900 invoked from network); 30 Dec 2002 19:37:34 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 30 Dec 2002 19:37:34 -0000 Received: (qmail 20484 invoked by uid 97); 30 Dec 2002 19:38:31 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 20468 invoked by uid 97); 30 Dec 2002 19:38:31 -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 20456 invoked by uid 98); 30 Dec 2002 19:38:30 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <00f001c2b03a$d86d2ae0$59096d50@pc1> From: =?iso-8859-1?Q?Julian_L=F6ffelhardt?= To: "Tomcat Users List" Subject: reducing tomcat & jasper memory footprint Date: Mon, 30 Dec 2002 20:37:10 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00ED_01C2B043.3A149500" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPart_000_00ED_01C2B043.3A149500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I'm using Apache 1.3.26 and 3 tomcat 4.0.4 instances with AJP13 & = loadbalancing . Our application is a CMS where all the published articles are generated = offline as JSP-Files, one jsp per article. We had hige problems with the memory footprint. Due to the fact that = every jsp is generated as a class and there are about 200 new artices = per day the permanent segment of the JVM heap gets filled with all the = classes, and I get an OutOfMemoryError. My workaround for now is setting -XX:PermSize and --XX:MapPermSize to = higher values, but this just delays application hang-up. With 64 megs of permSize our Server had an approx. uptime of 1 day now = it's about 3-4 days. Is there any way to unload jsp-Files (unload the class) ? llap, julian ------=_NextPart_000_00ED_01C2B043.3A149500--