Hello Tom, I am facing a similar issue. Could you please send that piece of code that was causing you this error, just that snippet should be good.
Thanks Tom Price-3 wrote: > > Hi all, > > No more help required - I traced back all the references to the Request > objects and it did turn out to be a bug in my application code. One of > my tracing classes (written a long time ago, before we used Tomcat) was > caching all created Thread objects. So when Tomcat decided to allocate > new threads to process incoming requests (and un-referenced the old > ones), my application cached the old threads and they slowly leaked. > I'm assuming that Tomcat only does this when handling multiple > concurrent connections (i.e. threads are reused when handling > single-threaded connections), hence the fact that I could only reproduce > the problem when sending in concurrent requests. > > Thanks for everyone's suggestions. > > Tom. > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://old.nabble.com/Memory-leak-in-Tomcat-5.5.16-tp16335734p28454415.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
