MustGather: IBM Integrated Web Services (IWS) or Integrated Web Application Server (IAS) Instance on IBM i is Hung or Will Not Stop/End

Resolving The Problem

1. Open a 5250 session and get to a command line interface.
2. Type the command: 
   ENDJOB JOB(<job_number>/<job_user>/<job_name>) OPTION(*IMMED)
   This command will forcefully terminate the IWS/IAS job.  Please note that this should be used as a last resort, as it doesn't allow the server to clean up resources gracefully.
3. Replace <job_number>, <job_user>, and <job_name> with the actual values of the hung IWS job.  This could be the IWS/IAS HTTP Server or JVM job.
4. If the IWS/IAS instance does not end, gather further IWS/iAS job information using these CL commands:
   Gather multiple instances of these dumps over the hang period.  This will show the call stacks of the IBM i job or JVM threads.
   DSPJOB JOB(<job_number>/<job_user>/<job_name>) OUTPUT(*PRINT)
   DSPJOB JOB(<job_number>/<job_user>/<job_name>) OPTION(*PGMSTK) SLTTHD(*ALL) OUTPUT(*PRINT)
   WRKJVMJOB, Option 12 next to the IWS/IAS instance JVM job
5. Gather the spooled files created as well as the javacore.xxx.txt files, which will be located in the /www/<IWS_IAS_instance>/wlp/usr/servers/<IWS_IAS_instance>/ directory.  Upload these files to IBM Support for review.
6. After 10 minutes has passed since the ENDJOB CL command was executed, you can try ending the job abnormally using: ENDJOBABN JOB(<job_number>/<job_user>/<job_name>)
7. Collect data for your IWS/IAS instance using the instructions in the IBM document, MustGather: Integrated Web Services (IWS) / Integrated Application Server (IAS) Data Collection.   This will create a /tmp/collectorscripts/data/<IWS_IAS_instance>collector.zip file.  Upload this file to IBM Support for review.
8. Detailed information on how to upload data to IBM Support can be found here: https://www.ibm.com/support/pages/node/644037