WebSphere JVM Crash
Issue
-
The WebSphere JVM crashes when a particular MDM procedure is called.
-
The following failing stack trace is listed below from an IBM and Informatica analysis:
.
.
#9 0x00002aaaaace9c5d in structuredSignalHandler ()
from
/opt/IBM/WebSphere/AppServer/java/jre/lib/amd64/compressedrefs/libj9vm24
.so
#10 0x00002aaaab07d161 in masterSynchSignalHandler ()
from
/opt/IBM/WebSphere/AppServer/java/jre/lib/amd64/compressedrefs/libj9prt2
4.so
#11 <signal handler called>
#12 0x000000355d40a3e2 in _dl_relocate_object () from
/lib64/ld-linux-x86-64.so.2 << faling stack
#13 0x000000355d410da6 in dl_open_worker () from
/lib64/ld-linux-x86-64.so.2
#14 0x000000355d40ceb6 in _dl_catch_error () from
/lib64/ld-linux-x86-64.so.2
#15 0x000000355d41066c in _dl_open () from /lib64/ld-linux-x86-64.so.2
#16 0x000000355dc00f9a in dlopen_doit () from /lib64/libdl.so.2
#17 0x000000355d40ceb6 in _dl_catch_error () from
/lib64/ld-linux-x86-64.so.2
#18 0x000000355dc0150d in _dlerror_run () from /lib64/libdl.so.2
#19 0x000000355dc00f11 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2
#20 0x00002aaaab07e3cc in j9sl_open_shared_library ()
- From the native stack it is clear that failing function is _dl_relocate_object() in /lib64/ld-linux-x86-64.so.2, which is a OS library i.e Linux OS with terminated with with signal 11, Segmentation fault. From the javacore it is also confirmed that crash is in Module: /lib64/ld-linux-x86-64.so.2() At the time of this crash, the JDK is telling Linux to open a shared library. So this is a jni call. This call then goes into 6 different Linux function before it crashes.
Environment
- Red Hat Enterprise Linux 5.3
- WebSphere Application Server 6.1 running Informatica MDM
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
