Saturday, 4 July 2015

Heap dumps and java core files websphere portal

Memory issues :- Most of the applications have memory consumption issues. JVM unexpectedly shutdowns due to memory issues. To identify these type of issues we can check java core and heap dump values.

Java core :- When JVM gets stopped unexpectedly javacore files will be generated it contains the mutliple threads which got hung during multiprocessing.

Heap dump :- Heap dump contains thread information with memory information these files can be manually read or imported in tools available online to identify the memory leak.

Process to generate heap dumps :- Up and running websphere portal is represented by PID. If we kill this process heap dumps will be generated.

Unix/linux ;-
kill -3 <PID>

Windows :- 
In task manager kill java.exe file

Location of heap dumps :- Under this location /IBM/WebSphere/AppServer/profiles/wp_profile/ we can find heap dumps.

Note:- native_stderr.log, containing the JVM messages, including garbage collection data if verbose
garbage collection is enabled. It's possible to configure a separate file to contain the verbose
garbage collection data, which would have a custom name, for example, Verbosegc.

No comments:

Post a Comment

Custom single threaded java server

 package com.diffengine.csv; import java.io.*; import java.net.*; import java.util.Date; public class Server { public static void main(Str...