1 Reply Latest reply on May 8, 2010 7:53 PM by S Crawford

    Java VM error when starting new app server

    S Crawford

      We are deploying new app servers into our environment and are encountering this issue when we try to start the them up for the first time.  We are running BL v7.5.0 on RHEL 4 32-bit, as root:

       

      $ more console.log
      [07 May 2010 18:25:23,649] [main] [INFO] [::] [] Starting Agent Service...
      [07 May 2010 18:25:23,652] [main] [WARN] [::] [] Trouble processing secureFilePath
      [07 May 2010 18:25:23,837] [main] [INFO] [::] [] Starting Configuration Service...
      [07 May 2010 18:25:23,890] [main] [INFO] [::] [] Configuration Service started.
      [07 May 2010 18:25:23,900] [main] [INFO] [::] [] Starting Content Importer Service...
      [07 May 2010 18:25:23,900] [main] [INFO] [::] [] Content Importer Service started.
      [07 May 2010 18:25:23,974] [main] [INFO] [::] [] Loading JNI libaries...
      [07 May 2010 18:25:23,981] [main] [INFO] [::] [] Loaded JNI library BlAsJni
      [07 May 2010 18:25:23,983] [main] [INFO] [::] [] Loaded JNI library XJNIService
      [07 May 2010 18:25:24,014] [main] [INFO] [::] [] Skipped Loading JNI library Atrium Core
      [07 May 2010 18:25:24,015] [main] [INFO] [::] [] Initializing JNI Configuration...
      #
      # An unexpected error has been detected by HotSpot Virtual Machine:
      #
      #  SIGSEGV (0xb) at pc=0x2c9825bd, pid=2458, tid=3086943936
      #
      # Java VM: Java HotSpot(TM) Server VM (1.5.0_10-b03 mixed mode)
      # Problematic frame:
      # C  [libnc.so+0x725bd]  blload_iconv+0x2b
      #
      # An error report file with more information is saved as hs_err_pid2458.log
      #
      # If you would like to submit a bug report, please visit:
      #   http://java.sun.com/webapps/bugreport/crash.jsp
      #

        • 1. Re: Java VM error when starting new app server
          S Crawford

          FYI, we resolved this issue.  The cause was the agent directory /usr/lib/rsc, on the app servers did not have execute access.  The bladmin account needs this access to read files in that directory and run nsh commands and nsh.

           

          Our workaround was originally to run the application servers as root (removing the su - bladmin in the init.d scripts).  Once this issue was fixed, we were once again to run the app servers as bladmin.