Re: Any synchronization issues with SMP?

2004-07-02 Thread Rainer Jung
TC clustering uses GZIP(In|Out)putStream in replication. I don't know, if there is buffering on top. Filip? Rainer Martin Schulz wrote: OT: The following is advice to servlet developers rather than container developers. For what it's worth, just be careful when you use GZIP(In|Out)putStream,

Re: Any synchronization issues with SMP?

2004-07-02 Thread Filip Hanik - Dev
, 2004 3:59 AM Subject: Re: Any synchronization issues with SMP? TC clustering uses GZIP(In|Out)putStream in replication. I don't know, if there is buffering on top. Filip? Rainer Martin Schulz wrote: OT: The following is advice to servlet developers rather than container developers

Re: Any synchronization issues with SMP?

2004-07-01 Thread Martin Schulz
OT: The following is advice to servlet developers rather than container developers. For what it's worth, just be careful when you use GZIP(In|Out)putStream, since the native code uses a mutex (for no good reason, imho), to prevent garbage collection from interfering with the array being used.

Re: Any synchronization issues with SMP?

2004-06-25 Thread Martin Schulz
it appears that the JVM slows everything down to a crawl, including the code path which should lead to another accept being called., for up to 8 minutes!!! Furthermore, the mpstat has the nice porperty that CPU usage adds up to exactly 100%, i.e. a single CPU is used... no more, no less. This

RE: Any synchronization issues with SMP?

2004-06-25 Thread Filip Hanik \(lists\)
Developers List Subject: Re: Any synchronization issues with SMP? it appears that the JVM slows everything down to a crawl, including the code path which should lead to another accept being called., for up to 8 minutes!!! Furthermore, the mpstat has the nice porperty that CPU usage adds up to exactly 100

Re: Any synchronization issues with SMP?

2004-06-23 Thread Rainer Jung
Hi, we know one application running on 9 systems with 4 US II CPUs each under Solaris 9. Peak request rates at 20 requests/second per system. Tomcat is 4.1.29, Java is 1.3.1_09. No symptoms like yours! You should send a signal QUIT to the jvm process during the unresponsiveness time. This is a

Re: Any synchronization issues with SMP?

2004-06-23 Thread Martin Schulz
Rainer, Thanks for the tips. I am about to take timing stats internally in the ThreadPool and the Tcp workers. Also, the described symptoms do not disappear, but seem to be of much shorter duration when only 4 CPUs are used for the application. I'll summarize what I find. Martin Rainer Jung