Server Crash in weblogic

Server Crash

    This implies the weblogic java process no longer exists.

    Server crash can occur only because of native code. (Java cannot cause a process to crash)

    Determine all potential sources of native code used by the WebLogic Server.

•         nativeIO.

•         Type2 jdbc driver.(We generally use thin driver for most  applications)

•         Native libraries accessed with JNI calls.

•         SSL native libraries.

•         JVM itself. Most of the times its from JVM.

    Sometimes the JVM will produce a small log file that may contain useful information as to which library the crash has originated from. (hs_err_pid*.log)

Server Crash Analysis

    When a JVM is crashed, a core file(binary image of the process) is created. Run pmap and pstack against the core file to get the library that caused the crash.

    Demo to figure out offending library using existing pmap & pstack out files.

Check list:

1) hs _err_pid*.log (Look for library that caused the crash)

2) pmap core (core file created in JVM root dir)

    pstack core

3) Using debugger (gdb,dbx,adb) (if above two steps does not provide any information)