From owner-freebsd-java@FreeBSD.ORG Mon Apr 20 15:41:42 2015 Return-Path: Delivered-To: java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 97F83953 for ; Mon, 20 Apr 2015 15:41:42 +0000 (UTC) Received: from messages.atlantisservices.net (atlantisservices.com [96.39.127.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6BBC736A for ; Mon, 20 Apr 2015 15:41:41 +0000 (UTC) Received: from desktop4.pathiakis.com (unknown [192.168.0.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by messages.atlantisservices.net (Postfix) with ESMTPSA id 20D111962A; Mon, 20 Apr 2015 15:41:34 +0000 (UTC) Message-ID: <55351E2D.60200@atlantisservices.net> Date: Mon, 20 Apr 2015 11:41:33 -0400 From: Paul Pathiakis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Lon Chen CC: "java@freebsd.org" Subject: Re: Freebsd + openjdk 7 = problem? References: <552F7FF0.5090909@eileo.com> <552FC8EC.5020509@atlantisservices.net> <55351A66.7030007@eileo.com> In-Reply-To: <55351A66.7030007@eileo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2015 15:41:42 -0000 You could try. The issue become that OpenNMS also encountered problems with linux-sun-jdk17. However, it was intermittent. Sometimes OpenNMS would run for as long as a day before core'ing. On various Linux platforms, no such issue. So, I'm going to assume there might be a problem with a syscall somewhere in the translation. *shrug* You may not have that problem and it could work fine. As I said, OpenNMS is making big use of all the features in the JDKs as they advance. P. On 04/20/2015 11:25, Lon Chen wrote: > 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@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@eileo.com >>> Phone: +33 1 53 01 21 98 >>> Hertz / EILEO -www.eileo.com >> > > -- > Lon CHEN > Software Architect > lon.chen@eileo.com > Phone: +33 1 53 01 21 98 > Hertz / EILEO -www.eileo.com