Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-1352

Fast-jar not working perfectly using openj9-11 s2i s390x Java OpenShift image

    XMLWordPrintable

Details

    • Hide

      1. log into OCP cluster on IBM Z

      2. git clone and checkout `2.2` branch of https://github.com/quarkus-qe/quarkus-test-suite.git

      git clone https://github.com/quarkus-qe/quarkus-test-suite.git
cd quarkus-test-suite
git checkout 2.2

      3. download maven repository zip for quarkus 2.2.3.CR5

      wget -q -O quarkus-maven-repo.zip http://download.devel.redhat.com/rcm-guest/staging/quarkus/quarkus-2.2.3.CR5/rh-quarkus-2.2.3.CR5-maven-repository.zip
unzip -q quarkus-maven-repo.zip -d /tmp/

      4. run the openshift tests (You can use module http/jaxrs-reactive as well)

      mvn -B -V clean verify \
-pl monitoring/micrometer-prometheus \
-fae \
-Dmaven.repo.local=/tmp/rh-quarkus-2.2.3.GA-maven-repository/maven-repository/ \
-Dquarkus.platform.version=2.2.3.Final-redhat-00013 \
-Dquarkus-plugin.version=2.2.3.Final-redhat-00013 \
-Dquarkus.platform.group-id=com.redhat.quarkus.platform \
-Dquarkus.platform.artifact-id=quarkus-bom \
-Dopenshift \
-Dall-modules \
-Dquarkus.s2i.base-jvm-image=registry.redhat.io/openj9/openj9-11-rhel8 \
-Dts.global.s2i.quarkus.jvm.builder.image=registry.redhat.io/openj9/openj9-11-rhel8 \
-Dts.global.s2i.maven.remote.repository=http://10.0.139.54:8040/artifactory/quarkus-maven-repo-zip
      Show
      1. log into OCP cluster on IBM Z 2. git clone and checkout `2.2` branch of https://github.com/quarkus-qe/quarkus-test-suite.git git clone https: //github.com/quarkus-qe/quarkus-test-suite.git cd quarkus-test-suite git checkout 2.2 3. download maven repository zip for quarkus 2.2.3.CR5 wget -q -O quarkus-maven-repo.zip http: //download.devel.redhat.com/rcm-guest/staging/quarkus/quarkus-2.2.3.CR5/rh-quarkus-2.2.3.CR5-maven-repository.zip unzip -q quarkus-maven-repo.zip -d /tmp/ 4. run the openshift tests (You can use module http/jaxrs-reactive as well) mvn -B -V clean verify \ -pl monitoring/micrometer-prometheus \ -fae \ -Dmaven.repo.local=/tmp/rh-quarkus-2.2.3.GA-maven-repository/maven-repository/ \ -Dquarkus.platform.version=2.2.3.Final-redhat-00013 \ -Dquarkus-plugin.version=2.2.3.Final-redhat-00013 \ -Dquarkus.platform.group-id=com.redhat.quarkus.platform \ -Dquarkus.platform.artifact-id=quarkus-bom \ -Dopenshift \ -Dall-modules \ -Dquarkus.s2i.base-jvm-image=registry.redhat.io/openj9/openj9-11-rhel8 \ -Dts.global.s2i.quarkus.jvm.builder.image=registry.redhat.io/openj9/openj9-11-rhel8 \ -Dts.global.s2i.maven.remote.repository=http: //10.0.139.54:8040/artifactory/quarkus-maven-repo-zip

    Description

      In a brief discussion with the Quarkus QE team, it seems like the default quarkus package type `fast-jar` is not working perfectly with the s390x openj9/openj9-11-rhel8 s2i Java OpenShift image. There are 2 specific test cases that are more consistent with failures, OpenShiftHttpCachingResourceIT and OpenShiftPrimeNumberResourceIT. I have tested these 2 test cases with the s390x ubi8/openjdk-11 and it didn't result in any failures. A temporary work-around provided by Jose of using older package type `quarkus.package.type=uber-jar` passes successfully.

      Failure log for OpenShiftPrimeNumberResourceIT:

      https://master-jenkins-csb-runtimes-ibmzqe.apps.ocp-c1.prod.psi.redhat.com/view/RHOAR/job/Quarkus-2.x-Openshift4-RH8-OpenJ9-JDK11/81/consoleText

      Passing using `quarkus.package.type=uber-jar` for OpenShiftPrimeNumberResourceIT:

      https://master-jenkins-csb-runtimes-ibmzqe.apps.ocp-c1.prod.psi.redhat.com/view/RHOAR/job/Quarkus-2.x-Openshift4-RH8-OpenJ9-JDK11/80/consoleText

      Early investigation seems to indicate that the `/deployments/quarkus-run.jar` file is missing from the build and the deployment starts with error. I don't believe it should even be using the `runner.jar` file if we are using the default fast-jar packaging type.

      13:47:02,345 INFO  [app] [app-1-kqfjb-app] Starting the Java application using /opt/jboss/container/java/run/run-java.sh ...
13:47:02,345 INFO  [app] ERROR No such file /deployments/micrometer-prometheus-1.0.0-SNAPSHOT-runner.jar
13:47:02,345 INFO  [app] INFO exec  java -Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:/usr/share/java/jolokia-jvm-agent/jolokia-jvm.jar=config=/opt/jboss/container/jolokia/etc/jolokia.properties -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:+ExitOnOutOfMemoryError -cp "." -jar   
13:47:02,345 INFO  [app] Error: -jar requires jar file specification

       

      cc: lzhan@redhat.com redmark@redhat.com

       

      Attachments

        Activity

          People

            ikanello1@redhat.com Ioannis Kanellos
            dafu@redhat.com Dale Fu
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: