Hi, all

We have deployed a third party web application in tomcat which translates 
HTTP requests from web clients into CORBA commands. We are seeing large 
increases in memory which never seems to be released. The memory sizes are 
checked every day with the "ps -o time,etime,pcpu,pmem,vsize,rssize" 
command.

The third party suggests that the problems could be due to garbage 
collection configuration in tomcat and would like us first to consult with 
'tomcat experts'. 

If you have expertise with tomcat and are reading this could you please 
confirm for us:
1. Is there any garbage collection configuration in tomcat?
2. If the answer to 1. is yes, is it possible that the garbage collection 
configuration in tomcat could be causing a large amount of memory never to 
be released?
3. Is it possible that the garbage collection configuration in the JVM 
could be causing a large amount of memory never to be released?

The implementation details are Tru64 Unix, tomcat 5.0.19, SDK 1.4.1-1 (for 
Tru64 Unix from HP). We are aware of other memory leak issues reported in 
tomcat 5.0.19 and SDK 1.4.1-1 but we have been able to rule out these 
known problems as the cause of our memory leak.

Thanks
Kenny

Reply via email to