Reynir Hübner wrote: > Victor & the others.. > > I've tested tc 4.1.5 and I get very similar problems as I did with tc. 4.1.3. > > if I stress/load my application with 10*10 threads I get messages like this on the >stdout log : > > ThreadPool: Caught exception executing >org.apache.tomcat.util.net.TcpWorkerThread@422a3b, terminating thread > java.lang.OutOfMemoryError > <<no stack trace available>> > java.lang.OutOfMemoryError > <<no stack trace available>> > > I increased the memory for jvm to 256mb and now tomcat "runs", but executes >everything alot (aprox 15-20 times) slower than tc 4.03 so I'm sticking to that for >now, at least I would not use tc4.1.5 for production as it is right now.
I would be interested in finding out the cause of the leak (obviously). Fixing it is probably going to be really obvious once we find it. I assume it is Jasper. Did you find anything which would indicate otherwise ? Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
