When a WebSphere® Application Server
process terminates abnormally, particularly on AIX® platforms, it may
leave two files: javacore*.txt and core. When the javacore*.txt file does
not provide all the information needed, it is possible to run dbxtrace on
the OS core to gain information from the native stack. Before doing that,
execute the following simple command on the core file to see what
executable caused the failure:
#lquerypv -h core 6b0 64
The output of this command is neat, clean and easy
to read. Here is an example:
[root@wassup:/]-->lquerypv -h core 6b0 64
000006B0 7FFFFFFF FFFFFFFF 7FFFFFFF FFFFFFFF
|................|
000006C0 00000000 000007D0 7FFFFFFF FFFFFFFF
|................|
000006D0 00120000 1312C9C0 00000000 00000017
|................|
000006E0 6E657473 63617065 5F616978 34000000
|netscape_aix4...|
000006F0 00000000 00000000 00000000 00000000
|................|
00000700 00000000 00000000 00000000 00000ADB
|................|
00000710 00000000 000008BF 00000000 00000A1E
|................|
The executable is located between the pipes on the
right hand side of the output. In this case, the core was generated by
Netscape.
Use this command as another tool for WebSphere
Application Server problem determination.
|