tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: Found it - WAS: Memory leak
Date Fri, 16 Jan 2004 00:24:46 GMT

----- Original Message -----
From: "Remy Maucherat" <remm@apache.org>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
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: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>


Mime
View raw message