I did a fresh build this morning from the SVN trunk, and I see the memory leak with both NIO and APR connector.
For each browser I run, I have at most 3 active connections at a time. I think, acually there are at most 2 active connections per browser, because by default both IE and FireFox don't open more than 2 connections to a single server. Thus, if I use 4 browser instances for my test, I have at most 12 (or 8) active connections. Matthias -----Original Message----- From: Rémy Maucherat [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 4:58 PM To: Tomcat Users List Subject: Re: Memory Leak with Comet On 4/24/07, Reich, Matthias <[EMAIL PROTECTED]> wrote: > If memory allocation of Tomcat continues until I see messages like > > org.apache.coyote.http11.Http11NioProcessor: Error processing request > java.lang.OutOfMemoryError: Java heap space There are leaks that have been fixed in the NIO connector, which exist in 6.0.10. Regardless of the amount of waiting events in your queue, each active Comet connection will use resources. There is also at least one relatively recent thread talking about Comet issues. Rémy --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
