Hi, 

I had a similar problem with apache 1.3 and mod jk2. The httpd processes
kept growing and growing. I didn't have this problem when I was using jk1.2
so I suppose it's a problem with jk2. 

To prevent the httpd processes getting to big causing the server to crash /
running out of memory I just changed the MaxRequestsPerChild property in the
httpd.conf from 0 (unlimited) to 1500. This way a processe gets killed after
1500 accesses and all the memory bound to it gets released. Of course you
have to try which value suits your configuration best depending on the
amount of memory you got and the number of max clients.

Hope this helps
Thomas

-----Urspr�ngliche Nachricht-----
Von: Carl Olivier [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 18. Juni 2004 09:38
An: '[EMAIL PROTECTED]'
Betreff: mod_jk2 memory leak?


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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to