----- Original Message ----- From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Thursday, January 15, 2004 11:41 AM Subject: Re: Found it - WAS: Memory leak
> Bill Barker wrote: > >>Remy Maucherat wrote: > >> > >>>-1. There is no memory leak with this. > >>>ByteChunks/CharChunks are always reused. If new ones are created, they > >>>will be reused. > >> > >>Arg, I have to find something. > >>I know ! It's all Costin's fault ! > >> > >>I didn't think about the "scaling back" feature of the thread pool, to > >>be honest. It should be very easy to avoid the problem, by setting > >>maxSpareThreads to maxThreads. > > > > Also, Jk-Coyote doesn't pool threads, so the total number of Requests > > created will (slowly) grow over time. > > I'm almost certain JK doesn't register the RequestInfo objects. It > should (and it's a bug), but actually it doesn't. I tried to have the > status servlet work with JK also, and had partial fixes, but in the end, > I didn't find the feature too worthwhile (and my fixes were hacks), so I > forgot about it (good thing I did). > It registers it on line 475 of HandlerRequest. It's true that Jk doesn't do much else with the RequestInfo, but it does register it. > Rémy > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]