Websphere tutorial

In general we need thread dump and heap dump mainly to find the Out Of Memory exception Thread dump :- a snapshot of live running java threads in the application server                       KILL -3 <PID>   to generate a thread dump The other way and in real-time we use                     Java\jdk1.8.0_201\bin\jstack <pid> > file.out Heap dump :- a snapshot of live running java objects in the heap memory 1. Click Servers > Application servers in the administrative console navigation tree. 2. Click server_name >Runtime Performance Advisor Configuration. 3. Click the Runtime tab. 4. Select the Enable automatic heap dump collection checkbox. 5. Click OK. Provided a simple answer. If any doubts regarding it, post a comment.

Generally in trouble shooting mainly we concentrate on 1)Log files 2)Hung threads 3)OOM(OutOfMemory) 4)CPU starvation 5)Disk space issues 6)Web container issues Log Files Application Server ----> jvm logs -----------> SystemOut.log (Start,Stop,Application processes)                                                       -----------> SystemErr.log (server related errors)                                                               -----> ProcessLogs ------> NativeStdOut.log (Sun jdk related memory,GC,etc.,)                                               ...