mod_jk2 memory leak?

[Carl Olivier <ca...@zero-one.co.za>]

Greetings.

Ok, I posted yesterday about the fork attribute - no response yet and stuff.
Now I indicated that the fork setting of true *seemed* to have solved many
of my problems RE the apparent memory leak on my server.

I am now revising that statement in that the server now stayed up for 25
hours as opposed to the 12 or so it was before I set the fork init-param to
true.  So now I am where the OTHER memory leak is.  I have run profilers on
the server and cannot seem to find anything obvious in my code (in fact my
code seems to garbage collect very well and properly)...

I do recall certain posts on this list about a potential memory leak in
mod_jk2 - I am running Apache 2.0.49 with mod_jk2 connecting to Tomcat
behind.

Does anyone know if this was ever proved to be the case?  I will be
attempting to run the server on Tomcat standalone - to see if the memory
leak persists or not.

Anyway, any pointers would be welcome!

Regards,

Carl Olivier

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org