Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-98373

Always fork process for build-db and rebuild-hypersonic

    Details

      Description

      Right now, builds in Patcher can randomly fail with the following error while running the build-db task:

           [java] JVM args ignored when same JVM is used.
           [java] Loading file:/opt/dev/projects/github/liferay-fix-pack-builder-ee/build/projects/github/liferay-portal-ee/portal-impl/classes/system.properties
           [java] SLF4J: Class path contains multiple SLF4J bindings.
           [java] SLF4J: Found binding in [file:/opt/dev/projects/github/liferay-fix-pack-builder-ee/build/projects/github/liferay-portal-ee/util-slf4j/classes/org/slf4j/impl/StaticLoggerBinder.class]
           [java] SLF4J: Found binding in [jar:file:/opt/dev/projects/github/liferay-fix-pack-builder-ee/build/projects/github/liferay-portal-ee/lib/development/slf4j-simple.jar!/org/slf4j/impl/StaticLoggerBinder.class]
           [java] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
           [java] SLF4J: Actual binding is of type [com.liferay.util.sl4fj.LiferayLoggerFactory]
           [java] Loading file:/opt/dev/projects/github/liferay-fix-pack-builder-ee/build/projects/github/liferay-portal-ee/portal-impl/classes/portal.properties
      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      #  SIGSEGV (0xb) at pc=0x00007f14a5e5f9c0, pid=15921, tid=0x00007f1475401700
      #
      # JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
      # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops)
      # Problematic frame:
      # C  [libc.so.6+0x1519c0]  __memmove_ssse3+0x1a0
      #
      # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
      #
      # An error report file with more information is saved as:
      # /opt/dev/projects/github/liferay-fix-pack-builder-ee/build/projects/github/liferay-release-tool-ee/hs_err_pid15921.log
      #
      # If you would like to submit a bug report, please visit:
      #   http://bugreport.java.com/bugreport/crash.jsp
      # The crash happened outside the Java Virtual Machine in native code.
      # See problematic frame for where to report the bug.
      #
      Exception in thread "main" java.lang.Exception: The process returned the unexpected exit value of 134.
      	at builder.plugins.ExecKt.exec(Exec.kt:48)
      	at builder.plugins.ExecKt.exec$default(Exec.kt:10)
      	at builder.MainKt$patch$42.invoke(Main.kt:1888)
      	at builder.MainKt$patch$42.invoke(Main.kt)
      	at builder.UtilKt.featureToggleWrapper(Util.kt:9)
      	at builder.UtilKt.featureToggleWrapper$default(Util.kt:3)
      	at builder.MainKt.patch(Main.kt:1832)
      	at builder.MainKt.main(Main.kt:75)
      :run FAILED
      

      Since SIGSEGV is related to memory, it's possible that by sharing the same JVM as Ant when running the build-db and rebuild-hypersonic tasks, we're more likely to run into the error. We observed in testing that by forcing it to fork the process, builds that were constantly failing succeeded.

        Attachments

          Activity

            People

            • Assignee:
              minhchau.dang Minhchau Dang
              Reporter:
              minhchau.dang Minhchau Dang
              Participants of an Issue:
              Recent user:
              Minhchau Dang
              Engineering Assignee:
              Minhchau Dang
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since last comment:
                17 weeks, 6 days ago

                Packages

                Version Package