load-testing issues
we are in the process of load-testing out portal. We have been getting
varied results none of which are very good. our portal failed in two
seperate tests.. one failed at 65 users another failed at 230 users on
different nights. we have noticed an error appearing in the webserver
errors log file on our second portal at the exact time that the portal
started failing. that is also the server that had to be restarted both
times. I would like know if anyone has any clues as to what the fix
might be for the following error message.
[11/Oct/2001:21:34:55] failure ( 4970): Internal error: exception thrown
from the servlet service function (uri=/DesktopServlet):
java.lang.OutOfMemoryError, Stack: java.lang.OutOfMemoryError
[805 byte] By [
] at [2007-11-25 4:31:24]

Lee Mathis wrote:
> we are in the process of load-testing out portal. We have been getting
> varied results none of which are very good. our portal failed in two
> seperate tests.. one failed at 65 users another failed at 230 users on
> different nights. we have noticed an error appearing in the webserver
> errors log file on our second portal at the exact time that the portal
> started failing. that is also the server that had to be restarted both
> times. I would like know if anyone has any clues as to what the fix
> might be for the following error message.
>
>
> [11/Oct/2001:21:34:55] failure ( 4970): Internal error: exception thrown
> from the servlet service function (uri=/DesktopServlet):
> java.lang.OutOfMemoryError, Stack: java.lang.OutOfMemoryError
The error message indicates basically the servlet ran out of memory.
Portal uses a desktop cache, profile cache, template cache and session
cache in addition to the memory allocated for a single user session.
The minimum memory allocated to a single user session is approximately
500k and increases more with bigger the size of the user desktop.
Take a look at the jvm12.conf and make sure you set the maximum heap
size to approximately 805 K and redo your performance testing.
Also do a java -version and check out the jvm version you are using, I
would recommend 1.2.2_07 for better jvm performance ..
Karthik !
at 2007-6-29 2:39:12 >
