[
https://jira.jboss.org/browse/JBAS-7248?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on JBAS-7248:
------------------------------------
Instead of using JBoss profiler to capture the memory heap, I wonder if it would be less
pain, to use the jdk tools to generate a heapdump (perhaps via the Java
-XX:+HeapDumpOnOutOfMemoryError option). Then, we can use the Eclipse Memory Analyzer to
read the heap dump (should be easier to use the JBoss profiler at the moment). I would be
happy to help analyze the heap dump with MAT, which is currently the best OSS tool for
memory leaks. :)
Make classloader leak test Hudson job use JBoss Profiler JVMTI
--------------------------------------------------------------
Key: JBAS-7248
URL:
https://jira.jboss.org/browse/JBAS-7248
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Shelly McGowan
Fix For: 6.0.0.M4
After parent task is done, a subsequent improvement will be to pin the Hudson job to a
particular server that has the native libraries needed for JBoss Profiler/JVMTI. Then run
the jobs with JBoss Profiler. This will make the runs much more predicable, stable and
useful.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira