portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randy Watler (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-1072) Jetspeed 2.1.1 getting out of memory.
Date Mon, 26 Oct 2009 21:50:59 GMT

    [ https://issues.apache.org/jira/browse/JS2-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770223#action_12770223
] 

Randy Watler commented on JS2-1072:
-----------------------------------

If you could supply a heap dump from the JVM after it has thrown an OOME, that would be ideal.

For the Sun JVM, the easiest thing is to generate a heap histogram using this JVM option:

-XX:+PrintClassHistogram

and sending the process a SIGQUIT or pressing ^\ on Linux/Solaris or pressing ^C on Windows.


> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message