Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B155110516 for ; Fri, 25 Oct 2013 15:01:26 +0000 (UTC) Received: (qmail 409 invoked by uid 500); 25 Oct 2013 15:01:22 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 304 invoked by uid 500); 25 Oct 2013 15:01:22 -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 295 invoked by uid 99); 25 Oct 2013 15:01:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 15:01:21 +0000 X-ASF-Spam-Status: No, hits=4.0 required=5.0 tests=DC_IMAGE_SPAM_HTML,DC_IMAGE_SPAM_TEXT,DC_PNG_UNO_LARGO,HTML_IMAGE_ONLY_12,HTML_IMAGE_RATIO_04,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of carpentier.ch@gmail.com designates 209.85.215.169 as permitted sender) Received: from [209.85.215.169] (HELO mail-ea0-f169.google.com) (209.85.215.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 15:01:16 +0000 Received: by mail-ea0-f169.google.com with SMTP id k11so731699eaj.0 for ; Fri, 25 Oct 2013 08:00:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=TmyoDCL4yozRg9ik/GhWCDMKKudkmAbBssgPZ67fwhA=; b=DXr3f89C7XAu5iKpEG6HiGOjxP6+2KO+RNGVZ8nQCCzjy2umczRzTIZa/8Paysgh2L KZcZpDdJ+HtfKiCkwDhuXNGEmC9cRGjZsIJEyBE7BSQZv8iepb6xAhmtQMs+dxqVkvtz jB3YgYnJppcllzMRDlLJ4vL+U4eXwo56H552GaJEeS33hkXKy/i2cBUS3F9kJjzf9FhL vLp9wI8nxwnBVVfmRuZzcfVSDJ3TSCtoZV5wNbTGFNbAmw9WaFlsCttB0Cq/URzI0BP1 iMiadRpjYn+j4/Y9FpbkmRK8KUoS+i/8n5+04fBVQn72SaT2DFUtd9s4PyAw1ccnw2Ym fWJw== X-Received: by 10.14.99.129 with SMTP id x1mr1038217eef.91.1382713254598; Fri, 25 Oct 2013 08:00:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.204.129 with HTTP; Fri, 25 Oct 2013 08:00:34 -0700 (PDT) From: Christophe Carpentier Date: Fri, 25 Oct 2013 17:00:34 +0200 Message-ID: Subject: Strange behaviour when redeploying To: users@tomcat.apache.org Content-Type: multipart/related; boundary=001a11c36cda5deed404e9920494 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c36cda5deed404e9920494 Content-Type: multipart/alternative; boundary=001a11c36cda5deed304e9920493 --001a11c36cda5deed304e9920493 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello everyone! I've come into a strange problem using tomcat with one of our company's WAR file. The application works as a charm, but when using the manager to redeploy it, roughly one time out of two, the heap size explodes: [image: Images int=C3=A9gr=C3=A9es 1] Please note that the *used* heap does not - according to JVisualVM anyway. After that, everything hangs, and the tomcat stops responding, with CPU usage ranging from 60 to 100%. Also, this issue has been reproduced on several Tomcat version ranging from 7.0.32 to 8.0-RC5, and on several machines (all Windows though). Could anyone direct me to the clues to look for? I have no idea where to begin: Profiler tools, VM settings...? And has anyone else seen such a behaviour? Thanks in advance! Christophe --001a11c36cda5deed304e9920493 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello everyone!

I've come into a st= range problem using tomcat with one of our company's WAR file.
The application works as a charm, but when using the manager to redeploy = it, roughly one time out of two, the heap size explodes:
3D"Images
Please note that the used= =C2=A0heap does not - according to JVisualVM anyway. After that, everything= hangs, and the tomcat stops responding, with CPU usage ranging from 60 to = 100%.
Also, this issue has been reproduced on several Tomcat version ranging= from 7.0.32 to 8.0-RC5, and on several machines (all Windows though).

Could anyone direct me to the clues to look = for? I have no idea where to begin: Profiler tools, VM settings...? And has= anyone else seen such a behaviour?

Thanks i= n advance!
Christophe

--001a11c36cda5deed304e9920493-- --001a11c36cda5deed404e9920494--