1. Home
  2. Support
Article - CS297193

How to modify the path to Java executable when JRE is updated in Windchill RV&S / Integrity Lifecycle Manager 12 and later

Modified: 09-Aug-2023   


Applies To

  • PTC RV&S (formerly Integrity Lifecycle Manager) 12.0 to 13.2

Description

  • Beginning with Windchill RV&S (Integrity Lifecycle Manager) Version 12.0, JRE (Java Runtime Environment) is no longer bundled in product distributions
  • JRE is separately installed on the machine
  • Full path to java.exe is specified at Server / Client / Agent installation
  • What property needs to be updated accordingly in case JRE is updated (for example, from 8u172 to 8u191) and the path to java.exe is changed?
  • Following error occurs on launching Windchill RV&S/Integrity Lifecycle Manager client:
    • LaunchAnywhere Error:
      "Could not find a valid Java virtual machine.  You may need to reinstall a supported Java virtual machine."

      Error:
      "C:\Program Files\Windchill\RVSClient12\bin\integrityg.exe: Attempt to launch Integrity Client time out.  tosolve this please try the following:
      - Verify that the user you are logged in as has read and write permissions to  the Integrity Client install directory.
      - Make sure the Integrity Client install directory is the very first entry in the path"
  • Integrity Lifecycle Manager/Windchill RV&S Server fails to start
    • JVM logging enabled startup.log shows : 
      • DEBUG  | 2022/08/10 09:50:50 | Command[49] : start
STATUS | 2022/08/10 09:50:50 | Launching a JVM...
ERROR  | 2022/08/10 09:50:50 | Unable to start JVM: No such file or directory (2)
DEBUG  | 2022/08/10 09:50:50 | Signal trapped.  Details:
DEBUG  | 2022/08/10 09:50:50 |   signal number=17 (SIGCHLD), source="unknown"
DEBUG  | 2022/08/10 09:50:50 | Received SIGCHLD, checking JVM process status.
DEBUG  | 2022/08/10 09:50:50 | JVM process exited with a code of 1, setting the wrapper exit code to 1.
ERROR  | 2022/08/10 09:50:50 | JVM exited while loading the application.
DEBUG  | 2022/08/10 09:50:50 | JVM was only running for 0 seconds leading to a failed restart count of 8.
DEBUG  | 2022/08/10 09:50:50 | Waiting 60 seconds before launching another JVM.

         
This is a printer-friendly version of Article 297193 and may be out of date. For the latest version click CS297193