1 Reply Latest reply on Jul 26, 2017 8:30 PM by GravyKing

    JVM crashes after updating to kernel-3.10.0-514.21.2.el7.x86_64

    GravyKing

      R12.1.3 running on RHEL7.

      Just wondering if anybody has run across this yet. 

      Just patched our test servers to kernel-3.10.0-514.21.2.el7.x86_64 and started having issues.

       

      This was in the output of the concurrent request.

      # A fatal error has been detected by the Java Runtime Environment:

      #

      #  SIGBUS (0x7) at pc=0xf0585cc5, pid=21508, tid=4092668672

      #

      # JRE version:  (7.0_95-b14) (build )

      # Java VM: Java HotSpot(TM) Server VM (24.95-b01 mixed mode linux-x86 )

      # Problematic frame:

      # j  java.lang.Class.getClassLoader()Ljava/lang/ClassLoader;+0

      #

      # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

       

      So far the fix we have found is to revert back to an older kernel 3.10.0-514.2.2.el7.x86_64

       

      From some other research on RedHat's site it looks like the suggestion is to:

      "increase the Thread stack size of the JVM using -Xss2m. This will require you to restart the JVM".

       

      I'm not sure where that would be set though.  Not that we need to go with the newer kernel at this point just curious if this makes sense to anyone.

       

       

        • 1. Re: JVM crashes after updating to kernel-3.10.0-514.21.2.el7.x86_64
          GravyKing

          For anyone who runs into this there was an update provided.

          There is a new kernel version (3.10.0-514.26.2.el7.x86_64) that fixes the bug in the previous version (3.10.0-514.21.2.el7.x86_64)

          RHBA-2017:1674

          Type bugfix

          Title kernel bug fix update

          Issued 2017-07-04

          Updated 2017-07-04

          Reboot Suggested true

          Description

          The kernel packages contain the Linux kernel, the core of any Linux operating system.

          * Prior to this update, a bug in the kernel prevented executables from starting if the maximum process stack size (rlimit_stack) was set to a value below approximately 4 MB. This update fixes the search for unmapped address ranges (suitable gap) in unmapped_area() and unmapped_area_topdown() by ensuring that the gap_end is always larger than gap_start. As a result, executables can be started with a limited process stack size as expected. (BZ#1466138)

          All users are advised to upgrade to these updated packages, which fix this bug. The system must be rebooted for this update to take effect.