Hi Jose, Are you using Java 5.x(1.5.x) ? If so, you can watch your JVM's runtime behavior using the JConsole( in the JAVA_HOME/bin directory) ? It has helped me earlier on to debug OOM situations.
You need to restart your tomcat so that you can add the required parameters in your startup.bat/startup.sh script. Here's what I did to change my tomcat(5.5.17 but also works in any 5.x) to allow JMX monitoring (from JConsole). I just added the line after the label doneSetArgs ==================== :doneSetArgs set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote rem Execute Java with the applicable properties ==================== JConsole will let you monitor your memory usage and also track heap and non-heap memory. You can also force a gc on your tomcat JVM from JConsole. It lets you monitor various pools like Eden Space, Survivor, Tenured, Perm, Code Cache, Perm Gen rw, Perm Gen RO, etc. That should give you some insight into what is happening within Tomcat. for more info on JConsole, see http://www.onjava.com/pub/a/onjava/2004/09/29/tigerjmx.html BR, ~A On 8/28/06, José Renato <[EMAIL PROTECTED]> wrote:
Hi, I am loading the data to be displayed with display-tag component. The data lists has been saved as request attributes. I will look for profilers to check this situation better. Thank a lot, Bye. David Smith escreveu: > If you are sure the sessions are where your memory is going, is there > any way to reduce the session size? I would think a query for a large > amount of data should be a request scoped item or maybe even put on > the presentation layer with a taglib. > > You could also be hanging onto object references in other parts of > your code. Invalidating the session won't clean that up. > > Also there are profilers around that will give you an idea of memory > useage. Google is your friend. > > --David > > José Renato wrote: > >> Hi All, >> >> I have an web application deployed with Tomcat 5.0.28. In some cases >> my queries can bring back huge amounts of data. Looking Windows Task >> Manager I perceived the natural memory increase. I noticed that when >> I call my logout method (It calls session.invalidate()) or my user >> session expieres the memory is still in use, in other words, the >> memory is not cleaned. This process will cause OutOfMemoryException >> soon. I would like to undertand how can I discover why this happens >> and how can I fix it. >> >> Best regards, >> José Renato. >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- BR, Anjan Bacchu Summit Information Systems
