The last time we profiled Cocoon (3 or 4 months ago)we didn't find a memory leak. I suggest to use a profiling tool. Then you will find very quickly if Cocoon is the problem.
Carsten Carsten Ziegeler Open Source Group, S&N AG > -----Original Message----- > From: Antonio Gallardo [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 06, 2002 7:27 AM > To: [EMAIL PROTECTED] > Subject: [C2.1] Memory problem > > > Hi, > > I think we have detected another "bug" in the current CVS version of 2.1. > > I will try to explain it here: > > As suggested in the book: "Professional Apache Tomcat", ISBN > 1-861007-73-6, page 37, Subtitle "Heap Size". I was configured Tomcat > Engine 4.1.12 with the following params: > > JAVA_OPTS='-Xms256m -Xmx256m -XX:NewSize=128m -XX:MaxNewSize=128m' > > This sustancially improves the performance of the Cocoon engine. The > server serves pages faster. > > But the problem is that is seems like the Java process is slowly "eating" > all the memory. Using the "top" command in Linux and after 2 days of works > the main Java process shows that is using more than 390MB! > > As I noted before in the server are 384 MB of RAM and it runs only Cocoon > Application. We does not use any custom component. All the application is > done using standard XSP logicsheets. > > Can someone has similars problems? Is this a Cocoon problem? > > Thanks in advance, > > Antonio Gallardo. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
