Collecting MustGather data for Out of Memory issues

Collect diagnostic information to resolve Out of Memory (OOM) issues before contacting .

Before you begin

Verify that you have administrative credentials and the required access permissions. Ensure that the disk has enough space; heap dumps are often several gigabytes (GB) in size.

Procedure

Generating Heap and Java Dumps for WebSphere Application Server (ts-app)
1. Navigate to the WAS bin directory:
```
cd <WAS_HOME>/bin
```
2. Start the wsadmin tool:
```
./wsadmin.sh -lang jython
```
3. Identify the JVM process:
```
set jvm [$AdminControl queryNames
      WebSphere:type=JVM,*]
```
4. Verify the JVM value:
```
puts $jvm
```
5. Generate the heap dump:
```
./server javadump <serverName> --include=heap
```
6. Collect the files from:
```
/opt/WebSphere/Liberty/usr/servers/<serverName>/cores/container/<containerId>/
```
- Generate Java cores: You can collect javacore data by killing the running server process using the kill -3 command.
Generating Heap and Java Dumps for WebSphere Liberty (Search, Store, or Customization)
1. Navigate to the Liberty bin directory:
```
cd /opt/WebSphere/Liberty/bin
```
2. Identify the server name in
```
/opt/WebSphere/Liberty/usr/servers
```
3. Generate the heap and Java dumps:
```
./server javadump <serverName> --include=heap
```
4. Collect the files from:
```
/opt/WebSphere/Liberty/usr/servers/<serverName>/cores/container/<containerId>/
```