[
https://issues.apache.org/jira/browse/JS2-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764690#action_12764690
]
Randy Watler commented on JS2-1072:
-----------------------------------
Please ensure that you are setting the JVM max memory size to something larger
than the default. If you are using the Sun JVM on a 32 bit machine, -Xmx512m is
typical for small numbers of concurrent users on Tomcat.
If you are setting this parameter, please supply the full set of JVM options
you are specifying along with information on your hardware environment.
Also, note that the POST-RELEASE branch of 2.1.3, (a.k.a. 2.1.4), has been
thoroughly tested and has a stable memory footprint. Please consider upgrading.
> Jetspeed 2.1.1 getting out of memory.
> -------------------------------------
>
> Key: JS2-1072
> URL: https://issues.apache.org/jira/browse/JS2-1072
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Application servers
> Environment: Windows
> Reporter: Nishant Malviya
> Fix For: 2.1.1-RC
>
>
> Jetspeed 2.1.1 is configured with MSSQL and is throwing out of memory with 13
> users. The jetspeed was throwing this exception even with derby database then
> we decided to move to MSSQL. The customer has 20 portal application and
> around 13 users working as of now.
> Can you give us the guidelines for the performance improvement for jetspeed
> 2.1.1. so that we can remove this out of memory exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
