Date: Mon, 27 Apr 2015 09:28:24 -0400 From: Paul Pathiakis <ppathiakis@atlantisservices.net> To: Ronald Roskens <roskens@elfin.net> Cc: Seth Leger <seth@opennms.org>, Benjamin Reed <ranger@opennms.org>, "freebsd-java@freebsd.org" <java@freebsd.org> Subject: Re: [opennms-devel] OpenNMS 1.14+ on FreeBSD 8, 9, 10, 11 Message-ID: <553E3978.3000201@atlantisservices.net> In-Reply-To: <198271CF-C8A8-469F-8C3F-159ABE12FD29@elfin.net> References: <551AFE89.2010407@opennms.org> <551AFF30.5000207@atlantisservices.net> <AA760E09-C8F2-47B4-8780-3903075E34C8@elfin.net> <551E1754.2040305@atlantisservices.net> <F105D0DC-2F9E-4818-A767-EC56709BCE08@elfin.net> <551F4455.7020305@atlantisservices.net> <679B4B28-35B8-4AD6-A84A-2E5C2E4BA77C@elfin.net> <5594D52C-56F5-411D-AC8E-0A9305DD0996@elfin.net> <5BB323E3-7697-4899-A740-C05109D9004A@opennms.org> <C35B77CA-AD2A-454B-86A6-20ACEB26BFA8@elfin.net> <C459D45F-010E-4C79-8C92-380C025FAC8A@elfin.net> <552148F6.1040708@atlantisservices.net> <7504A1F5-6C17-42D0-81E9-375C320235F5@elfin.net> <5522DEB3.2060407@atlantisservices.net> <30656E80-ECC3-4054-95C1-B42AEE0ECA56@elfin.net> <552FE3F1.50600@atlantisservices.net> <198271CF-C8A8-469F-8C3F-159ABE12FD29@elfin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Guys: http://www.opennms.org/wiki/Installing_on_FreeBSD_10.x_with_OpenJDK It's a first cut. It will need help. However, I can get this over to java@freeBSD.org so they can easily install and replicate the problem. P. On 04/20/2015 00:21, Ronald Roskens wrote: > Paul, > > I don’t think there’s been a change in status. The native FreeBSD OpenJDK 7 or 8 still crash. > > I’ve submitted pull requests today with fixes for the three test issues I found in OpenNMS. > > > There seems to be a regression with OpenJDK 8 on FreeBSD. I was looking at some of the hs_err_pid<pid>.log files and noticed that all id’s for the JavaThread lines have the same id, and that its the same as the PID of the process. OpenJDK 7 on FreeBSD works differently: it logs unique numbers for each, but there doesn’t seem to be any relation to either the tid or nid values logged in a thread dump. > > > > So I have $OPENNMS_HOME/etc/opennms.conf: > START_TIMEOUT=0 > JAVA_HEAP_SIZE=1024 > ADDITIONAL_MANAGER_OPTIONS=“-Xint -Xdiag" > > This makes the JDK run dog slow, it took around 35 minutes to startup. It crashed about 15 minutes later too. > > Its almost like once jetty is up and running, the JVM crashes. > > > > Here are my notes for installing OpenNMS 15 using the installer: > ==== > # pkg install openjdk7 > # pkg install bash > # pkg install jicmp > # pkg install jicmp6 > # pkg install iplike > > The installer requires an X11 display. > > # ftp 'http://sourceforge.net/projects/opennms/files/OpenNMS/stable-15.0.1/standalone-opennms-installer-15.0.1-1.zip/download' > # unzip standalone-opennms-installer-15.0.1-1.zip > # /usr/local/openjdk7/bin/java -jar standalone-opennms-installer-15.0.1-1.jar > Step 1: Information > Click Next > Step 2: Licensing Agreements > Click the radio button for 'I accept the terms of this license agreement.' > Click Next > Step 4: Target Path > Enter installation path: /usr/local/OpenNMS > Click Next > Message that /usr/local/OpenNMS target directory will be created. > Click OK > Step 5: Select Installation Packages > Select Core and Docs > Click Next > Step 6: User Data > Database Host: localhost > PostgreSQL Database Name: opennms > Database Port: 5432 > Database Username (Administrator): pgsql > Database Password (Administrator): <leave blank> > Database Username (Runtime): opennms > Database Username (Runtime): opennms > Click Next > Step 7: User Data - Configure Discovery Range > Start: <leave blank> > End: <leave blank> > Click Next > Step 8: Installation > ( this step extracts and installs into the target directory /usr/local/OpenNMS ) > Click Next > Step 9: Perform External Processes > ( this steps runs '/usr/local/OpenNMS/bin/install -dis' ) > Click Next > Step 10: Installation Finished > Click Done > > # vi /usr/local/OpenNMS/bin/opennms > Change #!/bin/bash to #!/usr/local/bin/bash > > Fix for NMS-7464 > # rm /usr/local/OpenNMS/jetty-webapps/opennms-remoting/WEB-INF/lib/org.opennms.core.soa-15.0.1.jar > > # /usr/local/OpenNMS/bin/opennms start > Open a web browser to <opennms-host-ipaddr>:8980 > Login using admin for username & password. > > ** need doc on setting up a requisition & single node ** > > Wait for the JDK to crash and dump an hs_err_pid<pid>.log and core file. > ==== > > > >> On Apr 16, 2015, at 11:31 AM, Paul Pathiakis <ppathiakis@atlantisservices.net> wrote: >> >> Guys, >> >> Sorry, I've been a little offline for a while. What is the status of everything? I know Ron corrected some things and I was just curious if everything is merged into 16 and in the repository. Also, how do I access the latest 16 stable branch (git command) ? >> >> I'd like to get the build process to be fully documented for the Java on FreeBSD folks so that they can easily reproduce all the unit tests and bugs as well as troubleshoot the OpenJDK8 to see what issues it has. >> >> Given 16 is on the way and so is 8, I figure that's a good direction to start in on. By the time they address the issues, we might be in sync with 16 and 8. Right now, nothing works and most people that were running previous versions of OpenNMS on FreeBSD are stuck on 1.12 or earlier and FreeBSD 9 or earlier. >> >> Thanks for everything so far! >> >> Paul >> >> >> On 04/06/2015 22:41, Ron Roskens wrote: >>> Search for the string HEAD, and you'll see the inline diff of changes. >>> >>> There is another way to install OpenNMS, by using the opennms-installer package. It's just a jar file you execute ( java -jar <file> ), then run through 10 install steps, and when completed, you have a fully working install ready for you to run $OPENNMS_HOME/bin/opennms start. It's saves time from having to run through the whole build process. It does require an X11 display, so I don't know how well that might go over for a port. >>> >>> What it would give a FreeBSD JVM developer though is a fully functional and running OpenNMS install they could test against. >>> >>> Ron >>> >>>> On Apr 6, 2015, at 2:29 PM, Paul Pathiakis <ppathiakis@atlantisservices.net> wrote: >>>> >>>> The merge generates a conflict, but its just a whitespace issue. >>>> >>>> vi features/system-report/src/main/java/org/opennms/systemreport/SystemReportResourceLocator.java >>>> git add features/system-report/src/main/java/org/opennms/systemreport/SystemReportResourceLocator.java >>>> git commit >>>> >>>> Ron, >>>> >>>> Regarding the above, where is the whitespace issue in that file? I'm kind of stuck looking for it. >>>> >>>> (Is there any way to correct it so that we don't have to change it each time we recheck the repository?) >>>> >>>> Also, given that I'm now told that JDK 1.8 is the way to go as 1.7 is EOL, I'm going to head in that direction. >>>> >>>> P. >>>> >>>> On 04/05/2015 18:00, Ronald Roskens wrote: >>>>>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?553E3978.3000201>