From users-return-115222-archive-asf-public=cust-asf.ponee.io@tapestry.apache.org Thu May 16 07:38:14 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8F82E18066B for ; Thu, 16 May 2019 09:38:14 +0200 (CEST) Received: (qmail 70139 invoked by uid 500); 16 May 2019 07:38:12 -0000 Mailing-List: contact users-help@tapestry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tapestry users" Delivered-To: mailing list users@tapestry.apache.org Received: (qmail 70127 invoked by uid 99); 16 May 2019 07:38:12 -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 May 2019 07:38:12 +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 124A7C0787 for ; Thu, 16 May 2019 07:38:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.302 X-Spam-Level: ** X-Spam-Status: No, score=2.302 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=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 JMivvsfouBgT for ; Thu, 16 May 2019 07:38:05 +0000 (UTC) Received: from smtp.outgoing.loopia.se (smtp.outgoing.loopia.se [194.9.95.112]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 7273861173 for ; Thu, 16 May 2019 07:38:04 +0000 (UTC) Received: from s554.loopia.se (localhost [127.0.0.1]) by s554.loopia.se (Postfix) with ESMTP id 41FF51F15247 for ; Thu, 16 May 2019 09:38:03 +0200 (CEST) Received: from s499.loopia.se (unknown [172.21.200.97]) by s554.loopia.se (Postfix) with ESMTP id 0B74479711C for ; Thu, 16 May 2019 09:38:03 +0200 (CEST) Received: from s471.loopia.se (unknown [172.21.200.36]) by s499.loopia.se (Postfix) with ESMTP id E34F71349A6A for ; Thu, 16 May 2019 09:38:02 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se Received: from s498.loopia.se ([172.22.191.5]) by s471.loopia.se (s471.loopia.se [172.22.190.11]) (amavisd-new, port 10024) with UTF8LMTP id 0FAuiXUR7FCD for ; Thu, 16 May 2019 09:38:02 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: mats.andersson@ronsoft.se X-Loopia-Originating-IP: 192.121.10.144 Received: from [192.168.0.101] (unknown [192.121.10.144]) (Authenticated sender: mats.andersson@ronsoft.se) by s498.loopia.se (Postfix) with ESMTPSA id 55D5E449513 for ; Thu, 16 May 2019 09:38:02 +0200 (CEST) Subject: Re: Laggy response after a quiet time To: users@tapestry.apache.org References: <1398EAF3-276A-4EF3-9EA3-84883E272C0A@gmail.com> From: Mats Andersson Message-ID: <15ee406d-a687-f6aa-7591-a6f552015758@ronsoft.se> Date: Thu, 16 May 2019 09:38:00 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <1398EAF3-276A-4EF3-9EA3-84883E272C0A@gmail.com> Content-Type: multipart/alternative; boundary="------------826ABA281A37FB7CE5521C8E" Content-Language: en-US --------------826ABA281A37FB7CE5521C8E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Do you have some scheduled services that could eat memory? I would suspect that the garbage collector is using most of that CPU. Monitor the GC and how memory is used over time. Maybe there is a mismatch between the memory configurations in Docker and the JVM. It seems like it is repeatable, that is good for troubleshooting at least. Mats On 2019-05-16 03:33, JumpStart wrote: > Hi all, > > My app is working brilliantly under load, but after a quiet time it can be very slow to respond, leading our first user of the day to tap the same thing multiple times, and the next thing you know is CPU hits 100% and is stuck there, and none of those requests returns a response. Nor do any new requests return a response. Apache logs show that all the requests time out after 60 secs, unanswered, and the health checkers start messaging the support staff. > > Has anyone else experienced this kind of thing? > > Perhaps it’s something to do with our infrastructure? We’re running Tapestry from an EAR in Wildfly in Docker in an AWS EC2 instance. Also in that EC2 instance is Apache HTTPD in Docker. > > Any thoughts, please! It’s a crazy problem. > > Cheers, > > Geoff > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org > For additional commands, e-mail: users-help@tapestry.apache.org > -- ---------------------- Mats Andersson | Ronsoft AB | +46(0)73 368 79 82 --------------826ABA281A37FB7CE5521C8E--