Quoting "Cozianu, Costin" <[EMAIL PROTECTED]>:
> Hi there,
>
> I just wanted to report the same problem, apparently the situation is
> improved in 3.2.2beta 2 .
>
> What I had is that under 3.1 and 3.2.1 when stress loaded with 50
> concurrent
> users making request each second Tomcat leaked memory.
> It would easily go to OutOfMemoryError, although I tried to help him by
> adding a servlet that fired the GC.
> So clearly it was a memory leak somewhere.
>
> I could have blamed my application for that but I did the same with
> other
> containers.
>
> Now the memory leak apparently has gone, but under the same stress
> Tomcat
> generates some extraneous errors (the problem was there before):
> "2001-03-30 12:32:38 - Ctx( /pictures ): IOException in: R( /pictures +
> /ImgCache
> /4/400/4003[cr_400]40030015.jpg + null) Connection reset by peer:
> socket
> write e
> rror"
> Is there a way to report these errors with some extra debug info ?
>
> Under no stress, the problem does not apear.
>
> Also the CPU usage for tomcat (800Mhz/256MB RAM)under 35
> requests/second
> goes to 50-60%,
> while for resin 1.2.3 it bearly touches 15%.
>
>
> So you're on the good path, but you still have a long way to go.
Maybe you should also test 3.3m2. It has big performance improvements, and is
much more efficient memory wise than 3.2.
Remy
