Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 May 2015 23:59:18 -0500
From:      Paul <pmcnary@cameron.net>
To:        freebsd-java@freebsd.org
Subject:   openNMS - core dump
Message-ID:  <555EB7A6.3010600@cameron.net>

next in thread | raw e-mail | index | archive | help
FreeBSD 10.1-RELEAE-p9 (amd64)
openJDK 1.8.0_40
openNMS 16.0.0

After building from source:
Had a problem building docs but that is another issue.

After starting openNMS it dumps core after a few minutes.
This problem was reported for a previous version of openNMS and openJDK7.

First part of dump is below.

Has any progress been made on this problem?
Can you give me any guidance on solving this issue?

I really want to run openNMS on FreeBSD 10.1+

Thank you

Paul
pmcnary@cameron.net

  Register to memory mapping:

RAX={method} {0x00000008760dfc50} '<init>' '(Ljava/lang/String;)V' in 
'java/net/SocketException'
RBX={method} {0x00000008760dfc50} '<init>' '(Ljava/lang/String;)V' in 
'java/net/SocketException'
RCX=0x0000000000000002 is an unknown value
RDX=0x000000082c992c88 is an oop
java.lang.String
  - klass: 'java/lang/String'
RSP=0x00007ffff02f5258 is pointing into the stack for thread: 
0x000000083473c000
RBP=0x00007ffff02f52e0 is pointing into the stack for thread: 
0x000000083473c000
RSI=0x000000082c992cd0 is an oop
java.net.SocketException
  - klass: 'java/net/SocketException'
RDI=0x00007ffff02f5380 is pointing into the stack for thread: 
0x000000083473c000
R8 =0x0000000803c786e0 is at code_begin+0 in an AdapterHandler
Adapter for signature: 0x0000000803c786e0 is at code_begin+0 in
[CodeBlob (0x0000000803c78690)]
Framesize: 0
BufferBlob (0x0000000803c78690) used for I2C/C2I adapters
R9 =0x00007ffff02f5678 is pointing into the stack for thread: 
0x000000083473c000
R10=0x0000000803c3245f is at begin+0 in a stub
StubRoutines::call_stub [0x0000000803c3245f, 0x0000000803c32547[ (232 bytes)
R11=0x0000000804e2e200 is at entry_point+64 in (nmethod*)0x0000000804e2e010
R12=0x00000008131ff000 is an unknown value
R13=0x00007ffff02f5270 is pointing into the stack for thread: 
0x000000083473c000
R14=0x000000083473c000 is a thread
R15=0x000000083473c000 is a thread


VM state:synchronizing (normal execution)

VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x000000080347bf00] Safepoint_lock - owner thread: 0x00000008034ea800
[0x000000080347bf80] Threads_lock - owner thread: 0x00000008034ea800

Heap:
  PSYoungGen      total 135168K, used 87638K [0x0000000828780000, 
0x0000000832e00000, 0x0000000833200
000)
   eden space 99840K, 84% used 
[0x0000000828780000,0x000000082da358d0,0x000000082e900000)
   from space 35328K, 8% used 
[0x0000000830b80000,0x0000000830e60020,0x0000000832e00000)
   to   space 35328K, 0% used 
[0x000000082e900000,0x000000082e900000,0x0000000830b80000)
  ParOldGen       total 253440K, used 207684K [0x0000000813200000, 
0x0000000822980000, 0x000000082878
0000)
   object space 253440K, 81% used 
[0x0000000813200000,0x000000081fcd11d0,0x0000000822980000)
  Metaspace       used 113328K, capacity 120418K, committed 120576K, 
reserved 1155072K
   class space    used 13059K, capacity 14487K, committed 14592K, 
reserved 1048576K

Card table byte_map: [0x0000000800662000,0x0000000800763000] 
byte_map_base: 0x00000007fc5c9000






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?555EB7A6.3010600>