This is usually caused by mismatched DB2® client and
server.
A possible stack:
SIGSEGV received at 0xd7203e70 in
/usr/WebSphere5/AppServer/java/jre/bin/classic/libjvm.a.
3XHSTACKLINE at 0xD71FB5CC in clFindClassFromClassLoader
3XHSTACKLINE at 0xD7203E70 in clLinkClass
3XHSTACKLINE at 0xD71F1C30 in clInitClass
3XHSTACKLINE at 0xD711AD34 in findFieldBlock
3XHSTACKLINE at 0xD5F898C0 in loadClasses
3XHSTACKLINE at 0xD5F8FEF4 in
Java_COM_ibm_db2_jdbc_app_DB2Driver_SQLAllocEnv
3XHSTACKLINE at 0xD714C8D0 in mmisInvoke_V_IHelper
3XHSTACKLINE at 0xD716EC70 in entryCmp
|