WebSphere Application Server & Liberty

 View Only

  • 1.  Unable to start JVM and nodeagent

    Posted Tue February 27, 2024 06:30 AM

    Hi can someone help me,

    recently we have upgraded our OS from RHEL-7 To RHEL-8, after upgrading OS we are unable to start jvm and nodeagent or dmgr. it's not run any command. same is the below output for any command.

    current WAS version is 8.5.5.24.

    -bash-4.4$ ./historyInfo.sh
    JVMJ9VM015W Initialization error for library j9jit29(11): cannot initialize JIT
    Error: Could not create the Java Virtual Machine.
    Error: A fatal exception has occurred. Program will exit.



    ------------------------------
    susheel kumar
    ------------------------------


  • 2.  RE: Unable to start JVM and nodeagent

    Posted Wed February 28, 2024 01:58 AM

    Hi susheer

    Though it's not sure, how about trying to clear jvm caches ?

    https://www.ibm.com/support/pages/how-clear-websphere-class-caches



    ------------------------------
    Yohji Amano
    ------------------------------

    Original Message


  • 3.  RE: Unable to start JVM and nodeagent

    Posted Wed February 28, 2024 09:46 AM

    Hi Yohji,

    Thanks for update ! 

    but main thing is that here we are getting the same exception for all command which we execute.



    ------------------------------
    susheel kumar
    ------------------------------

    Original Message


  • 4.  RE: Unable to start JVM and nodeagent

    Posted Thu February 29, 2024 12:02 AM

    Hi susheel.

    Apologies to not improving your situation.

    With regard to JVM cache, I think it's located under  /tmp/javasharedresources where name like C290M4F1A64P_webspherev85_1.8_64_bundled_root_G43L00 exists.

    So it may be one of trials to delete the cache file  directly, which I can think of right now.



    ------------------------------
    Yohji Amano
    ------------------------------

    Original Message


  • 5.  RE: Unable to start JVM and nodeagent

    Posted Fri March 01, 2024 02:54 AM

    Hello Susheel,

    just check the RLIMIT_MEMLOCK limit. RLIMIT_MEMLOCK defines how much memory an unprivileged process can lock. Locking a memory area protects it from swapping. (https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0079429)

    Maybe your settting with RHEL 8 is to low. 

    Did you get more information on that issue in native_stderr.log or native_stdout.log? 

    regards

    André



    ------------------------------
    Andre Jahn
    WebAdministrator
    Deutsche Bundesbank
    Duesseldorf
    1-555-555-5555
    ------------------------------

    Original Message


  • 6.  RE: Unable to start JVM and nodeagent

    Posted Thu February 29, 2024 03:52 AM

    Hi Susheel,

    Can you execute "cat /etc/security/limits.conf" in a terminal and share the results?

    Regards,



    ------------------------------
    Bernd van Oostrum
    Leuven
    32478808505
    ------------------------------

    Original Message


  • 7.  RE: Unable to start JVM and nodeagent

    IBM Champion
    Posted Fri March 01, 2024 05:29 AM

    Hi Susheel,

    did you reinstall WebSphere after upgrading the Linux version?

    I ask because the error message you are getting suggests that the Java process responsible for creating the JVM couldn't start.

    The JVM will have code that makes calls to the underlying operating system libraries and it is possible that the locations that the pointers point to have changed within the operating system libraries.

    I have assumed that your version of WebSphere is compatible with RHEL 8.

    If that doesn't work then consider raising a call with IBM.



    ------------------------------
    Mark Robbins
    Support Lead/Technical Design Authority / IBM Champion 2017 - 2023
    Cohesive (previously Vetasi Limited)
    https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/
    ------------------------------

    Original Message