Generating Java Core Dumps

About this task

Run the following command from any client connected to the OpenShift or Kubernetes cluster:
- OpenShift:
```
oc exec [asi-pod-name] -- ps -ef | grep NoAppServer
```
- Kubernetes:
```
kubectl exec [asi-pod-name] -- ps -ef | grep NoAppServer
```
Capture the child process ID, for example noapp-pid, and run the following command:
- OpenShift:
```
oc exec [asi-pod-name] --Kill -3 [noapp-pid]
```
- Kubernetes:
```
kubectl exec [asi-pod-name] --Kill -3 [noapp-pid]
```
The thread dumps will be generated within the pod and saved to the following log directory: ibm/trace/dumps/node1/

Note: The log directory node1 indicates the node number for the first ASI pod. Therefore, the second ASI pod will have the directory as node2, and so on.
Copy the logs to the client using the following command:
- OpenShift:
```
oc cp [asi-pod-name]:/ibm/trace/dumps/node1/ [local client path]
```
- Kubernetes:
```
kubectl cp [asi-pod-name]:/ibm/trace/dumps/node1/ [local client path]
```
If the log volume has been enabled and mapped to a shared file system location, then the dumps will be generated at the following mapped location: [mapped dir]/dumps/node1/