Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0CF47200D3E for ; Thu, 16 Nov 2017 20:25:17 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0B1A9160BEA; Thu, 16 Nov 2017 19:25:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 513551609EF for ; Thu, 16 Nov 2017 20:25:16 +0100 (CET) Received: (qmail 19446 invoked by uid 500); 16 Nov 2017 19:25:14 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 19435 invoked by uid 99); 16 Nov 2017 19:25:14 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2017 19:25:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B72BBC5F87 for ; Thu, 16 Nov 2017 19:25:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.721 X-Spam-Level: X-Spam-Status: No, score=-0.721 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 9m84cKux9Rsv for ; Thu, 16 Nov 2017 19:25:12 +0000 (UTC) Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com [209.85.216.179]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E6E945FCFB for ; Thu, 16 Nov 2017 19:25:11 +0000 (UTC) Received: by mail-qt0-f179.google.com with SMTP id f8so297344qta.5 for ; Thu, 16 Nov 2017 11:25:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=+wgFyPBxezx4Ax4y4s74qx8tzfgIj+gHYQdBMHOQugE=; b=e5r0bJgq3KuDu6IEVSX9ngtLTH3yyklCT5kbTiA/zjqmR1MgEi03+voRw07KlOjOWt zN2Fu/C9mMtk/1RKcKX0ZK1mR+bfYNmCgAl06Go9psikpA2UMvQYgCmAkj3x6VwuuAto z35bTvkOuHtDs0XOjfEvSLvxXS48vDRxsnl7yEPeGpBtojzcV8msGNLYN4bALGQkwW4z IbnyPyRcSyXTRL9s+FvKi2PI5PthequdN2KZMWziDhd7Mhp54vFmuM/ikq5byf3nhYTr XgbL6X8t87mP4WOZfzRDD5g/fav3vgthhK+08tXbii1gnoaZDBwUoS9oPo+md6mSjr7i MohA== X-Gm-Message-State: AJaThX6mHstEGbAR1e2RIWklaSmjdqKBAXjwT2CHB5D1a8h4fByRyVHg nLaTL3+4lB0xWeuMBYdv/aTQE2nCMpQtY8hJZXblZg== X-Google-Smtp-Source: AGs4zMYsuZQdqy135epeOFN0H5qocZNNQV50ykeK3vB0wD1AZJIvm53Jwk2ghdB8cf47Qz6ukQEDZYP6SpuojJjwt6c= X-Received: by 10.55.146.65 with SMTP id u62mr4285809qkd.358.1510860310408; Thu, 16 Nov 2017 11:25:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.56.193 with HTTP; Thu, 16 Nov 2017 11:25:09 -0800 (PST) In-Reply-To: References: From: Coty Sutherland Date: Thu, 16 Nov 2017 14:25:09 -0500 Message-ID: Subject: Re: Question - Tomcat Memory To: Tomcat Users List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable archived-at: Thu, 16 Nov 2017 19:25:17 -0000 On Thu, Nov 16, 2017 at 1:48 PM, Ramya Elineni wrote: > The "Initial memory pool" and "maximum memory pool" are the two configura= tions under Tomcat. I couldn't find any detailed explanation of how Tomcat = uses these settings. I request you to please provide me that informaiotn so= that I can have the appropriate values set on a production environment. We= are encountering issues where Tomcat is running on the higher end of the m= aximum memory pool configuration after about 25 days of its last restart. T= hanks. I assume that you're referring to the JVM arguments Xms and Xmx. There isn't a tomcat-specific setting to control JVM memory allocations; you'll need to read more about that in the java documentation of the appropriate JVM, but it isn't much more to the arguments than what you already stated. As far as 'appropriate values' goes, those are subjective because everyone's application's have different memory needs. You will have to do some load testing to determine how much memory your application will need to function properly. If your application is behavior abnormally and there are OutOfMemoryExceptions occurring you can also analyze a heap dump from the event to determine if you have an application problem causing memory issues, or if you just need more memory. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org