Dear OpenMeetings Developers, OM 3.1.2 does not start with JDK 1.8_u102, JDK1.8_u101, JDK1.8_u100. The log does not even start. The SSH tunnel to server is disconnected for all users in different locations. The only way to access the server is power it down and turn it on. This USE CASES is with 6 different NEW servers. Is there something that can be done here? Should we keep support for Java 1.7 until these crash reports from JDK 8 is taken care of by Oracle? (Internet search shows several JDK 8 crash reports for different reasons.)
OM 3.1.2 works fine with JDK1.7_u80 (the last Java 7 version) in the same servers with no crash. Environment of 6 different servers: 1. CentOS 7.3, MariaDB 10.x 2. CentOS 7.2, MariaDB 10.x 3. CentOS 7.1, MariaDB 10.x Thank you. Sincerely, Hemant K. Sabat Coscend Communications Solutions Web site: www.Coscend.com ------------------------------------------------------------------ CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages from Coscend Communications Solutions' posted at: http://www.Coscend.com/Terms_and_Conditions.html -----Original Message----- From: Maxim Solodovnik [mailto:solomax...@gmail.com] Sent: Monday, August 29, 2016 8:53 PM To: dev <dev@openmeetings.apache.org> Cc: om.insig...@coscend.com Subject: Re: [DISCUSSION] using JDK8 in OM https://issues.apache.org/jira/browse/OPENMEETINGS-1461 On Tue, Aug 30, 2016 at 8:49 AM, Maxim Solodovnik <solomax...@gmail.com> wrote: > Great, > > I'll update all branches > > On Tue, Aug 30, 2016 at 8:45 AM, seba.wag...@gmail.com < > seba.wag...@gmail.com> wrote: > >> I think that is acceptable. I would think we can safely update to >> Java8 for the screen sharing app. >> >> Thanks, >> Seb >> >> 2016-08-30 13:26 GMT+12:00 Maxim Solodovnik <solomax...@gmail.com>: >> >> > it's easy to test :) >> > open downloaded jnlp file change >> > <j2se version='1.7+'/> >> > to be >> > <j2se version='1.8+'/> >> > >> > and run it using Java7 >> > >> > you will get: >> > 1) warning from javaws: "Your java is too old, please update" >> > 2) another warning: "This application would like to use version of >> > Java 1.8+" >> > >> > On Tue, Aug 30, 2016 at 8:21 AM, seba.wag...@gmail.com < >> > seba.wag...@gmail.com> wrote: >> > >> > > Well another option is obviously compiling screen share with JDK8. >> > > >> > > As a client you only need JRE8 installed. According to some >> > > sources >> only >> > > roughly 50% of users have that: >> > > https://plumbr.eu/blog/java/java-version-and-vendor-data- >> > > analyzed-2016-edition >> > > >> > > What is the behaviour in case the Java version is too old? Will >> > > the >> > screen >> > > sharing app show a message saying "Please update Java" or will it >> > > just silently fail without any error or generic/cryptic message ? >> > > >> > > Thanks, >> > > Sebastian >> > > >> > > >> > > >> > > 2016-08-30 13:16 GMT+12:00 Maxim Solodovnik <solomax...@gmail.com>: >> > > >> > > > We can set "compilance level" to be 1.7, BUT screen-sharing >> > > > also >> > depends >> > > on >> > > > same mina :( >> > > > >> > > > OPENMEETINGS-1267 contains server log >> > > > >> > > > >> > > > On Tue, Aug 30, 2016 at 8:13 AM, seba.wag...@gmail.com < >> > > > seba.wag...@gmail.com> wrote: >> > > > >> > > > > Or is that attached exception in [OPENMEETINGS-1267] actually >> > > > > an >> > > > exception >> > > > > from the screen sharing applet ? Looks like an exception in >> > > > > the >> > server >> > > or >> > > > > not ? >> > > > > >> > > > > 2016-08-30 13:12 GMT+12:00 seba.wag...@gmail.com < >> > > seba.wag...@gmail.com >> > > > >: >> > > > > >> > > > > > Is it possible so set the build version for the screen >> > > > > > sharing >> > applet >> > > > to >> > > > > > Java7 separated from the server ? >> > > > > > >> > > > > > Thx >> > > > > > >> > > > > > 2016-08-30 13:09 GMT+12:00 Maxim Solodovnik < >> solomax...@gmail.com >> > >: >> > > > > > >> > > > > >> I'm also using java8 for all development (both 3.1 and >> > > > > >> 3.2) Why I raise this topic: red5-1.0.8-M9, we are using, >> > > > > >> depends on >> > > apache >> > > > > >> mina >> > > > > >> built with java8 >> > > > > >> this is why we have issues like this [1] >> > > > > >> >> > > > > >> [1] >> > > > > >> https://issues.apache.org/jira/browse/OPENMEETINGS-1267?fo >> > > > > >> cu sedCommentId=15445177&page=com.atlassian.jira.plugin. >> > > > > >> system.issuetabpanels:comment-tabpanel#comment-15445177 >> > > > > >> >> > > > > >> On Tue, Aug 30, 2016 at 5:54 AM, seba.wag...@gmail.com < >> > > > > >> seba.wag...@gmail.com> wrote: >> > > > > >> >> > > > > >> > Are you thinking of pushing the value for the source >> > > > > >> > code to >> > java >> > > > 1.8 >> > > > > ? >> > > > > >> > >> > > > > >> > @Hermant: No, if the Jar has compilation level set to >> > > > > >> > 1.8, a >> 1.7 >> > > JVM >> > > > > >> can't >> > > > > >> > execute it anymore. I am not sure, but I think WebStart >> > > > > >> > has >> some >> > > > > checks >> > > > > >> for >> > > > > >> > this and might display some error message saying you >> > > > > >> > have to >> > > update >> > > > > >> Java. >> > > > > >> > >> > > > > >> > I was building and running v3.2.x with JDK8 all the >> > > > > >> > time. Was >> > > doing >> > > > > >> fine. >> > > > > >> > However not set source code level to 1.8 yet. >> > > > > >> > >> > > > > >> > I think maybe migrate to JDK8 with the 3.2.x tree and >> > > > > >> > leave >> > source >> > > > > code >> > > > > >> > version to 1.7 for OpenMeetings 3.1.x >> > > > > >> > >> > > > > >> > Thanks, >> > > > > >> > Sebastian >> > > > > >> > >> > > > > >> > 2016-08-30 9:29 GMT+12:00 Coscend@OM < >> om.insig...@coscend.com>: >> > > > > >> > >> > > > > >> > > Hello Maxim, >> > > > > >> > > >> > > > > >> > > Build JDK 8 is great. >> > > > > >> > > >> > > > > >> > > Can the user's browser Java be 1.7 to use >> > > > > >> > > screensharing and >> > > > > recording? >> > > > > >> > > Or, should this be 1.8 as well? >> > > > > >> > > >> > > > > >> > > Thank you. >> > > > > >> > > >> > > > > >> > > Sincerely, >> > > > > >> > > >> > > > > >> > > Hemant K. Sabat >> > > > > >> > > >> > > > > >> > > Coscend Communications Solutions Web site: >> > > > > >> > > www.Coscend.com >> > > > > >> > > ------------------------------ >> ------------------------------ >> > > > ------ >> > > > > >> > > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice >> Regarding >> > > > E-mail >> > > > > >> > > Messages from Coscend Communications Solutions' posted at: >> > > > > >> > > http://www.Coscend.com/Terms_and_Conditions.html >> > > > > >> > > >> > > > > >> > > -----Original Message----- >> > > > > >> > > From: Maxim Solodovnik [mailto:solomax...@gmail.com] >> > > > > >> > > Sent: Monday, August 29, 2016 10:54 AM >> > > > > >> > > To: dev <dev@openmeetings.apache.org> >> > > > > >> > > Subject: [DISCUSSION] using JDK8 in OM >> > > > > >> > > >> > > > > >> > > Hello All, >> > > > > >> > > >> > > > > >> > > we currently have mix of JDKs in our libraries Maybe >> > > > > >> > > it's >> time >> > > to >> > > > > set >> > > > > >> > JDK8 >> > > > > >> > > as our build JDK? >> > > > > >> > > JDK7 is not being officially updated by Oracle anymore >> > > > > >> > > >> > > > > >> > > -- >> > > > > >> > > WBR >> > > > > >> > > Maxim aka solomax >> > > > > >> > > >> > > > > >> > > >> > > > > >> > > >> > > > > >> > > ----- >> > > > > >> > > No virus found in this message. >> > > > > >> > > Checked by AVG - www.avg.com >> > > > > >> > > Version: 2016.0.7752 / Virus Database: 4649/12902 - >> > > > > >> > > Release >> > > Date: >> > > > > >> > 08/29/16 >> > > > > >> > > >> > > > > >> > > >> > > > > >> > >> > > > > >> > >> > > > > >> > -- >> > > > > >> > Sebastian Wagner >> > > > > >> > https://twitter.com/#!/dead_lock seba.wag...@gmail.com >> > > > > >> > >> > > > > >> >> > > > > >> >> > > > > >> >> > > > > >> -- >> > > > > >> WBR >> > > > > >> Maxim aka solomax >> > > > > >> >> > > > > > >> > > > > > >> > > > > > >> > > > > > -- >> > > > > > Sebastian Wagner >> > > > > > https://twitter.com/#!/dead_lock seba.wag...@gmail.com >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > > -- >> > > > > Sebastian Wagner >> > > > > https://twitter.com/#!/dead_lock seba.wag...@gmail.com >> > > > > >> > > > >> > > > >> > > > >> > > > -- >> > > > WBR >> > > > Maxim aka solomax >> > > > >> > > >> > > >> > > >> > > -- >> > > Sebastian Wagner >> > > https://twitter.com/#!/dead_lock >> > > seba.wag...@gmail.com >> > > >> > >> > >> > >> > -- >> > WBR >> > Maxim aka solomax >> > >> >> >> >> -- >> Sebastian Wagner >> https://twitter.com/#!/dead_lock >> seba.wag...@gmail.com >> > > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.7752 / Virus Database: 4649/12907 - Release Date: 08/29/16
