Server Management - Systems Insight Manager
1751687 Members
5868 Online
108781 Solutions
New Discussion

Java VM error on mxstart

 
larsterca
New Member

Java VM error on mxstart

HPSIM 4.01, Linux Redhat ES3, Kernel 2.4.24.

I get this in the error log upon start of either mxinitconfig -a or mxstart

below is the hs_err_pid1742.log

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x0
Function=[Unknown.]
Library=(N/A)

NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.


Current Java thread:

Dynamic libraries:
08048000-08061000 r-xp 00000000 68:08 92283 /opt/mx/lbin/mxdomainmgr
08061000-08065000 rw-p 00018000 68:08 92283 /opt/mx/lbin/mxdomainmgr
40000000-40015000 r-xp 00000000 68:07 13218 /lib/ld-2.3.2.so
40015000-40016000 rw-p 00015000 68:07 13218 /lib/ld-2.3.2.so
40016000-4001a000 rw-s 00000000 68:07 3819 /tmp/hsperfdata_root/1742
4001c000-40029000 r-xp 00000000 68:07 39573 /lib/tls/libpthread-0.60.so
40029000-4002a000 rw-p 0000c000 68:07 39573 /lib/tls/libpthread-0.60.so
4002d000-405dc000 r-xp 00000000 68:08 46359 /opt/mx/j2re/lib/i386/server/libjvm.so
405dc000-40636000 rw-p 005ae000 68:08 46359 /opt/mx/j2re/lib/i386/server/libjvm.so
40649000-40659000 r-xp 00000000 68:08 61690 /opt/mx/j2re/lib/i386/libverify.so
40659000-4065b000 rw-p 0000f000 68:08 61690 /opt/mx/j2re/lib/i386/libverify.so
4065b000-40692000 r-xp 00000000 68:05 393517 /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
40692000-4069b000 rw-p 00037000 68:05 393517 /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
4069d000-406be000 r-xp 00000000 68:07 39571 /lib/tls/libm-2.3.2.so
406be000-406bf000 rw-p 00020000 68:07 39571 /lib/tls/libm-2.3.2.so
406bf000-407f1000 r-xp 00000000 68:07 39569 /lib/tls/libc-2.3.2.so
407f1000-407f5000 rw-p 00131000 68:07 39569 /lib/tls/libc-2.3.2.so
407f7000-40809000 r-xp 00000000 68:07 13235 /lib/libnsl-2.3.2.so
40809000-4080a000 rw-p 00011000 68:07 13235 /lib/libnsl-2.3.2.so
4080d000-4080f000 r-xp 00000000 68:07 13231 /lib/libdl-2.3.2.so
4080f000-40810000 rw-p 00001000 68:07 13231 /lib/libdl-2.3.2.so
40810000-40818000 r-xp 00000000 68:07 13193 /lib/libgcc_s-3.2.3-20031114.so.1
40818000-40819000 rw-p 00007000 68:07 13193 /lib/libgcc_s-3.2.3-20031114.so.1
4081a000-40822000 r-xp 00000000 68:08 61686 /opt/mx/j2re/lib/i386/native_threads/libhpi.so
40822000-40823000 rw-p 00007000 68:08 61686 /opt/mx/j2re/lib/i386/native_threads/libhpi.so
40823000-4082e000 r-xp 00000000 68:07 13251 /lib/libnss_files-2.3.2.so
4082e000-4082f000 rw-p 0000a000 68:07 13251 /lib/libnss_files-2.3.2.so
4082f000-4084f000 r-xp 00000000 68:08 61691 /opt/mx/j2re/lib/i386/libjava.so
4084f000-40851000 rw-p 0001f000 68:08 61691 /opt/mx/j2re/lib/i386/libjava.so
40851000-40865000 r-xp 00000000 68:08 61693 /opt/mx/j2re/lib/i386/libzip.so
40865000-40868000 rw-p 00013000 68:08 61693 /opt/mx/j2re/lib/i386/libzip.so
40868000-41f45000 r--s 00000000 68:08 46490 /opt/mx/j2re/lib/rt.jar
41f8f000-41fa5000 r--s 00000000 68:08 46367 /opt/mx/j2re/lib/sunrsasign.jar
41fa5000-4207d000 r--s 00000000 68:08 46376 /opt/mx/j2re/lib/jsse.jar
4207d000-4208e000 r--s 00000000 68:08 46368 /opt/mx/j2re/lib/jce.jar
4208e000-425d6000 r--s 00000000 68:08 46488 /opt/mx/j2re/lib/charsets.jar

Heap at VM Abort:
Heap
def new generation total 5504K, used 0K [0x44680000, 0x44e80000, 0x44e80000)
eden space 2816K, 0% used [0x44680000, 0x44680048, 0x44940000)
from space 2688K, 0% used [0x44940000, 0x44940000, 0x44be0000)
to space 2688K, 0% used [0x44be0000, 0x44be0000, 0x44e80000)
tenured generation total 24576K, used 0K [0x44e80000, 0x46680000, 0x66c80000)
the space 24576K, 0% used [0x44e80000, 0x44e80000, 0x44e80200, 0x46680000)
compacting perm gen total 16384K, used 277K [0x66c80000, 0x67c80000, 0x6ac80000)
the space 16384K, 1% used [0x66c80000, 0x66cc57f0, 0x66cc5800, 0x67c80000)

Local Time = Wed Jun 9 23:49:52 2004
Elapsed Time = 0
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_03-b02 mixed mode)
1 REPLY 1
David Claypool
Honored Contributor

Re: Java VM error on mxstart

Open this as a support case with customer services. That's the best (and official) way to get this escalated and looked at by the developers.