Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » loadtesting RAP 1.5.0. until OutOfMemory
loadtesting RAP 1.5.0. until OutOfMemory [message #1021572] Wed, 20 March 2013 06:26 Go to next message
Marcus Kalthoff is currently offline Marcus Kalthoff
Messages: 5
Registered: October 2011
Junior Member
Hi,

we have done a load test on our rap 1.5.0 application and the memory has grown until max heap.

We did a test, where 115 users have been simulated. After each testrun, new sessions have been created.

What we have seen in the heapdump are for example 2778

org.eclipse.rwt.internal.service.SessionStoreImpl

instances. Is it expected, that we have this number under this scenario? Should they not have been removed after session timeout (30 min)? Is there a know issue?
Re: loadtesting RAP 1.5.0. until OutOfMemory [message #1022453 is a reply to message #1021572] Thu, 21 March 2013 18:48 Go to previous message
Ralf Sternberg is currently offline Ralf Sternberg
Messages: 1286
Registered: July 2009
Senior Member

Hi Markus,

that's not a known issue and it's likely not even a RAP issue. If there
was such a severe memory leak in 1.5, it would have been noticed. When a
session times out, the session store should vanish, unless there are
references that prevent it from being GC'd. I'd suggest that you create
a heapdump and check the references to these instances.

Regards, Ralf


--
Ralf Sternberg

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Previous Topic:determine whether the RAP application is running from the IDE or from a JEE container
Next Topic:RAP 2.1 M1 is available
Goto Forum:
  


Current Time: Fri Apr 18 19:32:40 EDT 2014

Powered by FUDForum. Page generated in 0.04394 seconds