Thanks for the clear statement! As I do see processing objects that are not recycled, I now know that I have to postpone my efforts of using the CometProcessor interface. Maybe I'll retry with Tomcat 6.1 when it is released ;-)
If some day you like to take a look at a situation where processing objects are not recycled - feel free to ask me for an updated version of my test webapp which reflects my findings of this week. Regards, Matthias > -----Original Message----- > From: Rémy Maucherat [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 26, 2007 1:04 PM > To: Tomcat Users List > Subject: Re: Memory Leak with Comet > > On 4/26/07, Reich, Matthias <[EMAIL PROTECTED]> wrote: > > The clear semantics of this approach would be: Processing > is the same as for synchronous requests , except that the > RequestProcessor thread is released from processing early, > and another thread (or several threads that synchronize when > accessing the request) continues processing at any time it > wants, and the application fully controls the lifetime of > CometRequest instances. > > > > Thanks for the theories and the suggestions. However, it is not going > to be possible to make the API changes you suggested (since I don't > like them), and I also don't see a situation where the processing > objects are not recycled. > > 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]
