ing_5.html
-Original Message-
From: Peter Crowther [mailto:[EMAIL PROTECTED]
Sent: Martes, 29 de Agosto de 2006 11:29 a.m.
To: Tomcat Users List
Subject: RE: Handling huge amount data
> From: Robert Harper [mailto:[EMAIL PROTECTED]
> I've seen the memory rise and fall so if the G
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/
> From: Robert Harper [mailto:[EMAIL PROTECTED]
> I've seen the memory rise and fall so if the GC releases
> memory, it should be returned to the OS.
... at some point, assuming the GC is capable of compacting the heap to
give an entirely free block of memory that can be returned to the OS,
and
hultz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 29, 2006 9:44 AM
To: Tomcat Users List
Subject: Re: Handling huge amount data
José,
> Looking Windows Task
> Manager I perceived the natural memory increase.
>
> I noticed that when I
> call my logout method (It calls session
José,
> 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.
Windows only reports the size of
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
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 reference
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
exp
