that's an academic exercise for you, in the meantime, add in this option to
your startup options
-XX:-DisableExplicitGC
Filip
On 7/28/2011 1:07 PM, Alejandro Henao González wrote:
I dont believe that have GC running all the time, but the GC is called in the
above line to HTMLEncoder.encode. as follows.
System.gc();
resultado = htmlEncoder.encode(resultado);
response.reset();
may be this the problem? why?
Thanks.
----- Mensaje original -----
De: "Filip Hanik - Dev Lists"<devli...@hanik.com>
Para: "Tomcat Users List"<users@tomcat.apache.org>
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=10 tid=0x00002aaab31ea000 nid=0x47b2
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 problem.
On 7/28/2011 9:09 AM, Alejandro Henao González 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 executes
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 manager
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úcluos
incluso hasta los 8 a veces), y en consecuencia mi
aplicación web trabaja demasiado lento.
Tengo el Tomcat 7.0.14 en Redhat RHLE 5.5
La solución temporal que tengo es reiniciar el servicio, sin embargo esta no es
una solución práctica (pues debe ser un servidor 24/7). Es
posible configurar algún timeout para hilos en la etapa de servicio, o alguna
solución alternativa para este problema?
Muchas Gracias. Adjunto una imagen del reporte del estado por el tomcat
Manager, y el uso de la CPU
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
