Revision as of 09:44, 9 March 2017

This page collects the guidelines for the migration of D4Science infrastructure and the gCUbe software from Java 7 to Java 8. It also collects common issues (and their solution) experienced during the migration as reference for all gCube developers.

There are (few) documented incompatibilities between Java 7 and Java 8.

Running into one of them will require to re-factor the component and release a new version of it.

Java 8 compatibility guide: http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html

Source Code

Source Incompatibilities

• Detected at integration time (the component does not build)
• animal-sniffer-maven-plugin can be used by developers to detect them at development time

Dependencies

Some third-party libraries are not compiled in Java 8 and their code is not Java 8 compatible. This is usually the case of very old versions.

• lombok
  • not compatible: 0.11.6
  • suggested: 1.14.8

Behaviour Incompatibilities

• Cannot be detected at development and integration time
• We will need to carefully test our artifacts

Other Incompatibilities

• TOMCAT incopatibilities

Java8 required as pre-requisited the latest TOMCAT version as reported in the https://support.d4science.org/issues/6306:

Moving to the latest tomcat version is not so easy. We want to stuck with the distribution provided tomcat for a lot of reasons:

• backport of bug and security fixes
• compatibility with the apr libraries
• In addition to that, the javassist exceptions were a cosmetic only problem in the past, and an upgrade to a newer version of javassist was planned.

The solution is :

• for gCore : updating the xerces and xml-api libraries to make the gCore services working;
• for Smartgears: upgrade on ubuntu 14.04 all the development and production infrastructure. This should be resolved the problems manifested for the javassist and xml parsing.

Due to the split of the release in gCore and Smartgear components the migration and possible resolution of the issue are provided both.

• ETICS and javaws incompatibilities

Some issues with artifact built by ETICS are provided. In particular with SmartExecutor which runs on Smartgears. Such issues does not happen if the user try to build locally SmartExecutor, SmartgearsDistribution and SmartgearsDistributionBundle.

In particular If the user set this dependency on SmartExecutor

 <dependency> 
  <groupId>com.sun.xml.ws</groupId> 
  <artifactId>jaxws-rt</artifactId> 
  <version>2.1.7</version> 
 </dependency> 

The java.lang.IllegalArgumentException: Argument(s) "type" can't be null at com.sun.xml.bind.api.TypeReference. <init>(TypeReference.java:89) ~[jaxb-impl-2.1.11.jar:2.1.11] is occurred. The full description of the exception can be found at : https://support.d4science.org/pastes/740ec053e84ac34cb1118ac5084cec1a6dbb2374.

Trying to use the following version depdencendy for jaxws:

<dependency> 
  <groupId>com.sun.xml.ws</groupId> 
  <artifactId>jaxws-rt</artifactId> 
  <version>2.2.10</version> 
</dependency> 

another exception is occured :

The java.lang.RuntimeException: MASM0015: Class [ com.sun.xml.ws.assembler.jaxws.HandlerTubeFactory ] does not implement [ com.sun.xml.internal.ws.assembler.dev.TubeFactory ] interface at com.sun.xml.internal.ws.assembler.TubeCreator. <init> (TubeCreator.java:63) ~[na:1.8.0_121].

The full description can be found at: https://support.d4science.org/pastes/4ca7a2dd23215b6f5ce7a620412abc9db16ec12e.

The issues doesn't happen with the build locally for SmartExecutor, SmartgearsDistribution and SmartgearsDistributionBundle. The local configuration user is:

Oracle Java 8, 
$ java -version 
java version "1.8.0_121" 
Java(TM) SE Runtime Environment (build 1.8.0_121-b13) 
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) 

and

maven-compiler-plugin 3.6.2 

In the ETICS node the following configuration is used:

Java version: 1.8.0_91, vendor: Oracle Corporation 
Java home:  
/home/gbuilder/ workspace.org.gcube.4-3-0/repository/ externals/jdk/1.8.0_91/linux_x86_64/jre  
maven-compiler-plugin to 3.6.1 

jaxb version is inherited from javaws-rt (jaxb-impl is the 2.1.11). That's occurred when the user try to update javaws-rt to obtain a more recent version of jaxb. With javaws-rt 2.2.10 (the highest available on maven central) it's given jaxb-impl 2.2.10-b140802.1033 (2010 beta version) which seems too the latest available. - Problem javaws-rt is not a SmartExecutor requirement but is needed from common libraries to made calls and the problem is a runtime problem throw from dependency of dependency.

• Solution:

The user local build works fine , only remote build doesn't work. The solution seems from compiler point of view otherwise it could have a huge impact on common library development.
It was caused by a compilatoin or java runtime bug fixed in one of the patches between jdk 1.8.0_91 and jdk 1.8.0_121.

Updating of the jdk 8u121 in ETICS to test the artefactbuild in ETICS. The change is made permanent and set the jdk version for candidate release builds.

• Incompatibilities during the updating of the registry service (node9-d-d4s) #6306

In particular the issue occurred after the replacing of Xerces and xml-api libraries, where the gCore container doesn't start with the following exception:

2017-02-16 17:20:20,037 FATAL contexts.GHNContext [Initialiser,fatal:76] [0.663s] GHNContext: gHN could not complete initialisation
java.lang.NoSuchMethodError: org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar([Lorg/apache/xerces/xni/parser/XMLInputSource;)V
        at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(Unknown Source)
        at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638)
        at org.gcube.common.resources.kxml.KGCUBEResource.getSchema(KGCUBEResource.java:170)
        at org.gcube.common.resources.kxml.KGCUBEResource.load(KGCUBEResource.java:80)
        at org.gcube.common.resources.kxml.node.KGCUBEHostingNode.load(KGCUBEHostingNode.java:18)
        at org.gcube.common.core.contexts.GHNContext.loadGHNResource(GHNContext.java:405)
        at org.gcube.common.core.contexts.GHNContext.configureGHNResource(GHNContext.java:384)
        at org.gcube.common.core.contexts.GHNContext.initialise(GHNContext.java:291)
        at org.gcube.common.core.contexts.GHNContext.<clinit>(GHNContext.java:261)
        at org.gcube.common.core.contexts.GCUBEServiceContext$Initialiser.onRIDeployed(GCUBEServiceContext.java:677)
        at org.gcube.common.core.contexts.service.Consumer.onEvent(Consumer.java:30)
        at org.gcube.common.core.utils.events.GCUBEProducer$2.run(GCUBEProducer.java:176)

Solution: see you the previous issue to solve it.

JVM

JVM memory management changed in Java 8: concept of PermGen space has been replaced by Metaspace. As consequence, startup options used in Java 7 (e.g. "-XX:MaxPermSize") rae not valid anymore in JVM 8.

*node12-d-d4s.d4science.org (it'll replace node13.d.d4science.research-infrastructures.eu)
*node13-d-d4s.d4science.org (it'll replace node15.d.d4science.research-infrastructures.eu)
*node14-d-d4s.d4science.org (it'll replace node20.d.d4science.research-infrastructures.eu)

References

• Oracle releases plan

http://www.oracle.com/technetwork/java/eol-135779.html

• New features in Java 8
  • http://www.oracle.com/technetwork/java/javase/8-whats-new-2157071.html
  • https://leanpub.com/whatsnewinjava8/read

• Compatibility guide

http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html

• Animal Sniffer Plugin Guide

https://blog.gvsig.org/2011/07/25/hunting-api-incompatibilities-with-the-animal-sniffer-project/