[
https://issues.apache.org/jira/browse/JS2-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770955#action_12770955
]
Randy Watler commented on JS2-1072:
-----------------------------------
As noted above, the thread and heap dump is generated with a ^Break,
(Ctrl+Break), combination. On German keyboards, the Break key is Untbr. Of
course, that works only on processes started in the MSDOS console.
There is another utility out on the net that one might be able to use for
windows: SendSignal.exe,
(http://www.latenighthacking.com/projects/2003/sendSignal/). I assume that one
would find the heap and stack traces in the standard output logs.
C:\> SendSignal <process id of jvm>
If you are using JDK 1.6, there is a utility jmap that can be used to generate
the histogram heap snapshot by attaching to the target JVM,
(http://java.sun.com/javase/6/docs/technotes/tools/share/jmap.html).
C:\> jmap -histo:live <process id of jvm>
> 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]
