(GO) WebSphere memory overflow, manually export the PhD and Javacore files for was

Original: https://www.cnblogs.com/zhengbn/p/3499700.html

1: Server-to-server type-->websphere Application Server

2: Click to enter Server1

3: If it's was7.

Server infrastructure---management--custom properties

If the WAS6.

Java processes and management-environment entries

4: Create the following properties separately, and remember to save, and be careful not to have extra spaces

Name value
Ibm_heapdump TRUE
Ibm_heapdumpdir D:/WW
Ibm_heapdump_outofmemory TRUE
Ibm_heap_dump TRUE
Ibm_javadump_outofmemory TRUE
Ibm_java_heapdump_text TRUE

5: Restart WebSphere after confirmation, otherwise it will not take effect

6: Open cmd, go to WebSphere installation directory, <was_home>\appserver\bin, execute Wsadmin.bat

To export Javacore commands:

Set JVM [$AdminControl completeobjectname type=jvm,process=server1,*]

$AdminControl Invoke $JVM Dumpthreads

To export heapdump commands:

Set objectName [$AdminControl querynames websphere:type=jvm,process=server1,*]

$AdminControl Invoke $objectName Generateheapdump

7: Export Javacore****.txt:

Export Heapdump****.txt:

It's normal if you don't throw it wrong.

The exported file is

Was7 in: <was_home>\appserver\profiles\appsrv01 (including. phd files and. txt files)

WAS6 in: D:ww folder

：

Note:

The currently known analysis tools

Ha452.jar

Ha39.jar

Others, but did not try, not much to say.

(GO) WebSphere memory overflow, manually export the PhD and Javacore files for was