From owner-freebsd-java@FreeBSD.ORG Mon Apr 6 01:57:27 2015 Return-Path: Delivered-To: java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37785F6A for ; Mon, 6 Apr 2015 01:57:27 +0000 (UTC) Received: from messages.atlantisservices.net (atlantisservices.net [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 06A19CC5 for ; Mon, 6 Apr 2015 01:57:26 +0000 (UTC) Received: from [192.168.0.6] (unknown [192.168.0.6]) (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 05B6C19E57; Mon, 6 Apr 2015 01:57:18 +0000 (UTC) Message-ID: <5521E7FE.3090600@atlantisservices.net> Date: Sun, 05 Apr 2015 21:57:18 -0400 From: "ppathiakis@atlantisservices.net" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: java@freebsd.org, Ronald Roskens Subject: Fwd: Re: [opennms-devel] OpenNMS 1.14+ on FreeBSD 8, 9, 10, 11 References: <7504A1F5-6C17-42D0-81E9-375C320235F5@elfin.net> In-Reply-To: <7504A1F5-6C17-42D0-81E9-375C320235F5@elfin.net> X-Forwarded-Message-Id: <7504A1F5-6C17-42D0-81E9-375C320235F5@elfin.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Apr 2015 01:57:27 -0000 Forwarding to the java on freebsd project...... Hi Java! We have issues here that are problems with openjdk 7 and 8. Please acknowledge and confirm so we can all work on this together and get this resolved asap. I would like to see OpenNMS in the ports tree soon and this has already gone on for more than 6 months. Thank you! P. -------- Forwarded Message -------- Subject: Re: [opennms-devel] OpenNMS 1.14+ on FreeBSD 8, 9, 10, 11 Date: Sun, 5 Apr 2015 17:00:57 -0500 From: Ronald Roskens To: ppathiakis@atlantisservices.net > On Apr 5, 2015, at 9:38 AM, ppathiakis@atlantisservices.net wrote: > > Ron, > > Any hints on what I'm doing wrong with git and why it won't check out the develop section that you're providing. Also, if 1.8 is working with 1.16, I'm going to head in that direction for testing if that sounds good. > > Use my resources as you need to get things done. I'm here to help and learn so that I can support the FreeBSD port in the future. (Unless you want to run with it.) If the develop branch already exists, then # git checkout develop You should also pull up the latest commits. # git pull Then you could do the git merge. When I run OpenNMS 16.0.0-SNAPSHOT (develop) with either OpenJDK7 or OpenJDK8, I get a JVM crash dump. When I had installed OpenJDK7 and 8, I noticed there were config options for debugging. For both the slowdebug and fastdebug options, I re-installed OpenJDK8 and ran OpenNMS. Both times the JVM crashed within minutes of startup. Is there a way to compile OpenJDK8 using GCC rather than clang? Is there a way to compile OpenJDK8u60-b09 within the FreeBSD ports framework and use that to test running OpenNMS under? I found this PDF from Oracle on troubleshooting guide for Java SE 6, and assume it also applies to OpenJDK. http://www.oracle.com/technetwork/java/javase/tsg-vm-149989.pdf There were two JVM arguments that I found that are supposed to help debugging JNI or native methods. “-verbose:jni” and “-Xcheck:jni” and both arguments when added to the command line for OpenNMS caused the JVM to crash much earlier. Create the file $OPENNMS_HOME/etc/opennms.conf and add a line ADDITIONAL_MANAGER_OPTIONS=“Xcheck:jni -verbose:jni” and you’ll get the crash. As Jessie had posted earlier, one of the FreeBSD java port developers is needed to help diagnose it further from here. Ron