| Profiling RAP Application [message #647520] |
Thu, 06 January 2011 13:39  |
Eclipse User |
|
|
|
Hi,
I'm using VisualVM to monitor and profile a RAP application and I've noticed that some instances from the classes of the application are not garbage collected once the rap application and the client's browser have been closed.
For example the classes that extend from ActionBarAdvisor, WorkbenchAdvisor, WorkbenchWindowAdvisor are some of these instances.
Does these instances suppose to be alive once the application has been closed?
If not, is there a way to release them so they can be garbage collected?
[Updated on: Thu, 06 January 2011 14:03] by Moderator |
|
|
|
|
|
| Re: Profiling RAP Application [message #648117 is a reply to message #648045] |
Tue, 11 January 2011 04:47  |
| Eclipse User |
|
|
|
On Mon, 10 Jan 2011 17:10:57 -0600, Jesus Luna Quiroga wrote:
> I'm setting to a 1000 the field session timeout of the runtime settings
> in the launch configuration of the application. I don't really know if
> the value are seconds or milliseconds, but I'm guessing that are
> milliseconds.
No, it's seconds, as the label says: "Session timeout [s]". To be able to
test session cleanup, you'll have to set it to a lower value. I'd
recommend ~30-60s, to be able to simulate some user interaction. Then you
wait for session timeout, create a heap dump, analyze it...
Regards, Ralf
--
Ralf Sternberg
Twitter: @ralfstx
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
Powered by
FUDForum. Page generated in 0.30786 seconds
Home