----- Original Message ----- From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Thursday, January 15, 2004 12:33 PM Subject: Re: Found it - WAS: Memory leak
> Bill Barker wrote: > >>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. > > Yes, I know the code exists and would look like it would work, but last > time I tried, all the JMX code in JK wasn't executed. For example, the > MBean for the ChannelSocket wasn't registered. > Did you put traces in there to double check ? > Yup, it seems that the JMX registration in Jk is broken. HandlerRequest never gets registered, so it never registers the RequestInfo. > I'm not very familar with JK, so I don't know for sure. Even if it's > registered, I don't know if it would be a problem or not. > If it was registered, it most definitely would be a memory leak. You would keep creating Request objects that never get dereferenced. > 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]
