Hi, your problem is Java 1.4.1_02, it has a memory leak in StringBuffer which is used a lot for XML parsing. Upgrade to 1.4.2 and it will be fine.
Pete On Monday 01 November 2004 22:25, Anand Narasimhan wrote: > Hi, > > I am not able to determine if the problem is related to tomcat, solaris or > the application itself. Any help/pointers to debug the problem will be > greatly appreciated. > > The application runs on Solaris 2.8 using Sun's Java version 1.4.1_02. The > tomcat version is 4.1.27. The GUI is written using HTML/JSP/Struts 1.0.2. > The database is Oracle version 8.x (I think). The application also has API > interface written using Java/XML/Soap etc. The application is memory/CPU > intensive. The problem I am having is, after running under a large load, > tomcat process's memory footprint (reported by top command) increases > rapidly to more that 2G. The heap size (max configured to 1G), increases to > about 500 - 600M. I have tried running tomcat with optimizeit to see if > there are any memory leaks. optimizeit as wells as the output from GC > (running with -verbose:gc, -XX+PrintGCDetails) shows frequent garbage > collection activity and the heap size does not grow too much. > > I am not able to figure out why the process memory grows. If the heap is > not growing too much, what is consuming the memory? > > Thanks > Anand > > _________________________________________________________________ > > Anand Narasimhan > [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
