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 D0E757EE4 for ; Thu, 28 Jul 2011 19:08:11 +0000 (UTC) Received: (qmail 95498 invoked by uid 500); 28 Jul 2011 19:08:08 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 95267 invoked by uid 500); 28 Jul 2011 19:08:07 -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 95258 invoked by uid 99); 28 Jul 2011 19:08:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2011 19:08:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [200.24.40.28] (HELO mail.dqingenieria.com) (200.24.40.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2011 19:08:00 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.dqingenieria.com (Postfix) with ESMTP id E86E6A46C1 for ; Thu, 28 Jul 2011 14:07:38 -0500 (COT) X-Virus-Scanned: amavisd-new at mail.dqingenieria.com Received: from mail.dqingenieria.com ([127.0.0.1]) by localhost (mail.dqingenieria.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-svMX9P5wha for ; Thu, 28 Jul 2011 14:07:33 -0500 (COT) Received: from mail.dqingenieria.com (localhost.localdomain [127.0.0.1]) by mail.dqingenieria.com (Postfix) with ESMTP id 36FD5A369F for ; Thu, 28 Jul 2011 14:07:33 -0500 (COT) Date: Thu, 28 Jul 2011 14:07:33 -0500 (COT) From: Alejandro Henao =?utf-8?Q?Gonz=C3=A1lez?= To: Tomcat Users List Subject: Re: Problem with threads in stage Service (Tomcat 7.0.14) Message-ID: <152dc955-313c-45b8-9a85-fa768376e442@correoDQ> In-Reply-To: <4E319DFC.4070508@hanik.com> Content-Type: multipart/alternative; boundary="=_24e1ca87-3208-4be8-8e5e-7cdbecdf83f2" MIME-Version: 1.0 X-Originating-IP: [192.168.33.11] X-Mailer: Zimbra 7.1.1_GA_3196 (ZimbraWebClient - SAF3 (Win)/7.1.1_GA_3196) X-Virus-Checked: Checked by ClamAV on apache.org --=_24e1ca87-3208-4be8-8e5e-7cdbecdf83f2 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I dont believe that have GC running all the time, but the GC is called in t= he above line to HTMLEncoder.encode. as follows. System.gc(); resultado =3D htmlEncoder.encode(resultado); response.reset(); may be this the problem? why? Thanks. ----- Mensaje original ----- De: "Filip Hanik - Dev Lists" Para: "Tomcat Users List" Enviados: Jueves, 28 de Julio 2011 12:35:56 Asunto: Re: Problem with threads in stage Service (Tomcat 7.0.14) most likely you have GC running all the time ""http-bio-80"-exec-107" daemon prio=3D10 tid=3D0x00002aaab31ea000 nid=3D0x= 47b2 runnable [0x00000000436ab000] java.lang.Thread.State: RUNNABLE at java.util.HashMap.get(HashMap.java:303) at sae.HTMLEncoder.encode(HTMLEncoder.java:46) this should not be a stage where you're stuck, unless you have a loop probl= em. On 7/28/2011 9:09 AM, Alejandro Henao Gonz=C3=A1lez wrote: > Good day. > > I have the following problem with my tomcat. > > Sometimes, some threads are keep in service stage for a long time (really= never exit from this stage), this causes that tomcat uses a > hight percentage of the CPU (100 % of 2 or 3 cores) thus the webapp execu= tes very slow. > > I have a Tomcat 7.0.14 in a Redhat RHLE 5.5. > > The partial solution is restart the service, but this is not a practical = solution(because is a 24/7 server). is posible config a timeout > for threads in service stage, or any solution?? > > Thanks. Sorry for the redaction. Attached an image with the tomcat manage= r status and the CPU consuming. > > > -------- > > Cordial saludo. > > Tengo el siguiente problema con mi tomcat. > En algunas ocasiones, algunos hilos se quedan en la etapa de servicio por= demasiado tiempo (de hecho nunca salen de esta etapa), esto > causa que el tomcat use un alto porcenta de la CPU (el 100 % de 2 o 3 n= =C3=BAcluos incluso hasta los 8 a veces), y en consecuencia mi > aplicaci=C3=B3n web trabaja demasiado lento. > > Tengo el Tomcat 7.0.14 en Redhat RHLE 5.5 > > La soluci=C3=B3n temporal que tengo es reiniciar el servicio, sin embargo= esta no es una soluci=C3=B3n pr=C3=A1ctica (pues debe ser un servidor 24/7= ). Es > posible configurar alg=C3=BAn timeout para hilos en la etapa de servicio,= o alguna soluci=C3=B3n alternativa para este problema? > > Muchas Gracias. Adjunto una imagen del reporte del estado por el tomcat M= anager, y el uso de la CPU > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org --=_24e1ca87-3208-4be8-8e5e-7cdbecdf83f2--