Freebsd + openjdk 7 = problem?
Lon Chen
lon.chen at eileo.com
Mon Apr 20 15:26:40 UTC 2015
Hi Paul,
thanks for your replies. I'll forward you and the community some of our
logs. I hope it will help narrow down the problem.
Aside from that, is it worth running the application with the linux
emulated jdk?
BR
Lon
Le 16/04/2015 16:36, Paul Pathiakis a écrit :
> Lon Chen,
>
> It's the FreeBSD community, nothing is a bother. ;-)
>
> No. Everything is still crashing with OpenJDK7. The sad part is the
> newest issue I'll face is that OpenNMS is going to 16 on their
> software and it will require a JDK 8 variant. FYI, JDK7 is dead very
> soon. There will be no support for it as Oracle is going to EOL 7.
> So, JDK8 will be the only JDK supported soon.
>
> I've been trying to get the FreeBSD Java people to pick this up and
> run with it to get OpenJDK to work correctly again. The OpenNMS
> people have made extensive patches to OpenNMS to support FreeBSD after
> I begged them to do so. However, I have heard nothing about progress
> being made to resolve the issues in weeks.
>
> I'm going to CC the people on the java at freebsd.org list.
>
> If you can send them crash dumps, that would be great.
>
> I'm still working with the OpenNMS people and I'm going to get a cheat
> sheet together on how to quickly implement a build and install so that
> someone in the java group can fix these issues.
>
> P.
>
>
> On 04/16/2015 05:25, Lon Chen wrote:
>> Hello Paul,
>>
>> I'm really sorry to bother you and to write you directly, but your
>> feedback with opennms on freebsd and jdk7 is really important to us.
>> I've been following your discussions about freebsd and jdk7, and I
>> would like to have some infos.
>>
>> We are currently trying to upgrade our homemade applications to
>> openjdk7 but, like you did, we had some random segmentation faults
>> that did not occur with openjdk6. It can happen within 10min or
>> within several days. Our applications were running smoothly on
>> openjdk6 and freebsd8.
>>
>> We are also trying to have our applications work with linux-jdk-7 but
>> it seems that you still had segmentation faults with it?
>> Finally, what do you mean when you say :
>>
>> "
>> Finally, the SIGSEV is the same error I was getting. Newer versions of
>> OpenNMS, OpenJDK7, and FreeBSD 10.1-STABLE may have changed that.
>> " ?
>> Does it mean that the problem disappeared with some new packages?
>>
>> Thanks in advance for your consideration.
>> --
>> Lon CHEN
>> Software Architect
>> lon.chen at eileo.com
>> Phone: +33 1 53 01 21 98
>> Hertz / EILEO -www.eileo.com
>
--
Lon CHEN
Software Architect
lon.chen at eileo.com
Phone: +33 1 53 01 21 98
Hertz / EILEO - www.eileo.com
-------------- next part --------------
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00000008035bc4e3, pid=20829, tid=36672485632
#
# JRE version: 7.0-b15
# Java VM: OpenJDK 64-Bit Server VM (23.21-b01 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# j java.net.SocketTimeoutException.<init>(Ljava/lang/String;)V+0
--------------- T H R E A D ---------------
Current thread (0x0000000860530000): JavaThread "pluginV3-14" [_thread_in_Java, id=1616283776, stack(0x00007fffec5cb000,0x00007fffec6cb000)]
siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x00007fffec6aae60
Registers:
RAX=0x0000000000000000, RBX=0x0000000806da0d08, RCX=0x0000000000001a01, RDX=0x000000080872f170
RSP=0x00007fffec6b8e60, RBP=0x00007fffec6b8ea0, RSI=0x00000008035bc3a0, RDI=0x00007fffec6b8f70
R8 =0x00000008035bc3a0, R9 =0x00007fffec6b91c0, R10=0x0000000806da0c00, R11=0x0000000802535ad0
R12=0x00000008065bf000, R13=0x0000000806da0cf8, R14=0x00007fffec6b8eb8, R15=0x0000000860530000
RIP=0x00000008035bc4dc, EFLAGS=0x0000000000000001, ERR=0x0000000000000006
TRAPNO=0x000000000000000c
......................
R9 =0x00007fffec6b91c0 is pointing into the stack for thread: 0x0000000860530000
R10=0x0000000806da0c00 is an oop
{constant pool}
- klass: {other class}
- holder: 0x0000000806da14a0
- cache: 0x000000080872f170
- 1 : : klass_index=4 name_and_type_index=17
- 2 : : klass_index=4 name_and_type_index=18
- 3 : : 'java/net/SocketTimeoutException'
- 4 : : 'java/io/InterruptedIOException' {0x806da11c0}
- 5 : : 'serialVersionUID'
- 6 : : 'J'
- 7 : : 'ConstantValue'
- 8 : : -8846654841826352300
- 10 : : '<init>'
- 11 : : '(Ljava/lang/String;)V'
- 12 : : 'Code'
- 13 : : 'LineNumberTable'
- 14 : : '()V'
- 15 : : 'SourceFile'
- 16 : : 'SocketTimeoutException.java'
- 17 : : name_index=10 signature_index=11
- 18 : : name_index=10 signature_index=14
- 19 : : 'java/net/SocketTimeoutException'
- 20 : : 'java/io/InterruptedIOException'
......................
Stack: [0x00007ffff8489000,0x00007ffff8589000], sp=0x00007ffff8577060, free space=952k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
j java.net.SocketTimeoutException.<init>(Ljava/lang/String;)V+0
v ~StubRoutines::call_stub
V [libjvm.so+0x563cd2] AsyncGetCallTrace+0xd3762
V [libjvm.so+0x562c98] AsyncGetCallTrace+0xd2728
V [libjvm.so+0x5631d9] AsyncGetCallTrace+0xd2c69
V [libjvm.so+0x48cf42] +0x2d0d62
V [libjvm.so+0x48d117] +0x2d0f37
V [libjvm.so+0x48d59f] +0x2d13bf
V [libjvm.so+0x577f81] JNI_CreateJavaVM+0x57d1
--------------- S Y S T E M ---------------
OS:BSDuname:FreeBSD 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Tue Jun 12 00:39:29 UTC 2012 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
rlimit: STACK 8192k, CORE 0k, NPROC 5547, NOFILE 200000, AS infinity
load average:2.47 2.52 2.16
CPU:total 8 (4 cores per cpu, 2 threads per core) family 6 model 30 stepping 5, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, ht, tsc, tscinvbit
/proc/cpuinfo:
<Not Available>
Memory: 4k page, physical 12197824k(3049456k free)
/proc/meminfo:
vm_info: OpenJDK 64-Bit Server VM (23.21-b01) for bsd-amd64 JRE (1.7.0_25-b15), built on Jan 21 2014 16:05:45 by "jym" with gcc 4.2.2 20070831 prerelease [FreeBSD]
time: Mon Mar 30 08:23:49 2015
elapsed time: 51 seconds
More information about the freebsd-java
mailing list