"http-443-205" daemon prio=10 tid=0x096a8400 nid=0x2a04 runnable
[0x3089d000..0x3089e130]
java.lang.Thread.State: RUNNABLE
at org.apache.tomcat.jni.Socket.sendbb(Native Method)
at
org.apache.coyote.http11.InternalAprOutputBuffer.flushBuffer(InternalAprOutputBuffer.
prio=10 tid=0x08ecfc00 nid=0xdd8 waiting on
condition
JNI global references: 811
Heap
PSYoungGen total 203456K, used 3336K [0xa9b9, 0xb7f10000,
0xb7f1)
eden space 172928K, 1% used [0xa9b9,0xa9ed2270,0xb447)
from space 30528K, 0% used [0xb614,0xb614,0xb7f100
On 31/03/2012 02:12, B.V. Prasad wrote:
> I am using Tomcat 6.0.16 in production. When I try to upgrade to
> Tomcat 6.0.35, I see high CPU (about 90% vs. about 20% for 6.0.16),
> all other things being equal, except that I had to set
> setBufferSize(16384) in HTTPResponse in order to disable chunke
I am using Tomcat 6.0.16 in production. When I try to upgrade to Tomcat 6.0.35,
I see high CPU (about 90% vs. about 20% for 6.0.16), all other things being
equal, except that I had to set setBufferSize(16384) in HTTPResponse in order
to disable chunked encoding (needed as some of my client appli
