This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
Kawa servlet leaks
- From: Chris Dean <ctdean at sokitomi dot com>
- To: "Dominique Boucher" <dboucher at nuecho dot com>
- Cc: "'Kawa List'" <kawa at sources dot redhat dot com>
- Date: Tue, 18 Nov 2003 22:44:12 -0800
- Subject: Kawa servlet leaks
- References: <000201c3ae3c$3cc43bf0$6400a8c0@Forman>
> I wrote a simple client application that sends 2000 requests to the
> servlet. The Tomcat process grows from 30Mb to 78Mb. I'm sure this is
> not normal. Any hint? [I will soon have to put a Kawa-based web
> application in production mode, so this is a critical issue for me.]
As Jim said, that might not be that strange. You could add some memory
statistics to your page (by calling Runtime.getRuntime().freeMemory(),
totalMemory(), etc.) and see if it changes over time. Make sure to
allow enough settle time to allow the GC thread to run before you take
the last measurement.
For what it's worth, we run Kawa in production settings. However, we
don't use the servlet interface like you do.
Regards,
Chris Dean