AS Java Startup issue

Java VM detection issues

The AS Java is not able to start due to trouble while detecting the properties of the Java Virtual Machine (JVM), the Java Runtime Environment (JRE) or the Java Software Development Kit (SDK).

For the AS Java, it is not sufficient to just have the Java Runtime Environment (JRE), because the AS Java needs the Java compiler during runtime to compile the JSPs and EJB stubs.

  • Check that you have installed a suitable Java environment in the location defined in the instance profile by the “jstart/vm/home” or “jstartup/vm/home” parameter. If neither of these parameters is set, check the JAVA_HOME environment value.
  • Check if there are multiple Java versions installed; make sure that the JEE Engine uses an appropriate version.
  • On UNIX systems, it is important to verify the user rights.

The result from the Java VM detection is stored in a *.jvm file in the work directory of the instance. This file can be safely deleted if it contains inaccurate information (e.g. a wrong path).

Java VM shared library issues

Check that the *.jvm file contains correct information – if not, delete the file.

  • In Windows systems, error code 193 indicates that the Java VM DLL has a different word length (32 or 64 bit) that the JStart program. In this case, the trace file contains the following error entry:

                *** ERROR => DlLoadLib: LoadLibrary(jvm.dll) Error 193

  • UNIX systems may create an error message containing

                 cannot open file

If the word length of the Java VM and the JStart program differ – even though the file named in the error message exists.

Java VM initialization issues
Problems with initializing the VM are often caused by incorrect parameters in the VM. For more detailed information, refer to the dev_<node> trace file (for example, dev_server0) or std_<node>.out trace file (for example, std_server0.out).

Examples of incorrect parameters:

  • Unknown parameters, e.g. -XX:someParam, result in the following error message:

                Command-line option unrecognised: -XX:someParam

Refer to the Java VM documentation for supported parameters and their Syntax.

  • 32-bit platforms only: The defined heap is too big; there is not enough contiguous virtual address space to allocate the heap. As a result, the Java VM issues the following error message:

               Could not reserve enough space for object heap.

For Windows systems, Note 835704 provides additional information. You can use the address space viewer (Note 736462 or Note 129813) and preload DLL (Note 853696) to resolve this issue.

Use the ConfigTool to correct the values in the AS Java configuration database. Restart the AS Java instance afterwards.

  • On Windows platforms, you cannot initialize the Java VM if another JVM.DLL exists in the %windir%\system32 directory. The error message in the dev_bootstrap file is:

                 Cannot create Java VM instance from library <name>

  • To confirm this issue, set the trace level to 3 and restart the instance. The system issues now the following message in the dev_bootstrap trace:

                 load shared library (jvm.dll), hdl <number>, addr <address> 

                 using “C:\WINDOWS\system32\jvm.dll”Delete the Java VM library copy in the %windir%\system32 directory.

Helpful Notes:
1303953 – SAP JVM memory parameters and their names in the Config Tool

Java program exit codes

Java node ‘<name>’ terminated with exit code <code>:

In the dev_bootstrap or dev_deployment trace file tells that the respective startup phase failed; they are accompanied by a “Failures in the <text> phase” message in the dev_jstart trace. Refer to the corresponding section below.

This message in a dev_server<n> file indicates some malfunction at the AS Java level or at some higher level; such issue requires a more detailed analysis.

Please refer “Troubleshooting guide” to search the exit code and possible error cause –
http://wiki.sdn.sap.com/wiki/display/TechTSG

Java process issues

  • Java VM crashed.Indicates that the Java VM failed for some reason. Typically, the failed server node is restarted automatically. Nevertheless, information about the crash shows up in the dev_server<N> trace files and in other files generated by the Java VM. For the SAP JVM, Note 1305395 provides additional advice.Helpful Notes:
    1305395 – SAP JVM crash: How to identify and what to do
  • Failures in the ‘deploying offline components’ phasePlease check note 1550641. If there is not any applicable solution for the problem, create a message for the BC-JAS-DPL component and attach a compressed archive containing the following files from the/usr/sap/<SID>/<instance>/workdirectory:dev_jstart*
    dev_deployment*
    std_deployment*
    jvm_deployment*
  • Failures in the ‘synchronizing binaries’ phasePlease create a message for the BC-JAS-COR component and attach a compressed archive containing the following files from the /usr/sap/<SID>/<instance>/workdirectory:dev_jstart*
    dev_bootstrap*
    std_bootstrap*
    jvm_bootstrap*
    log_bootstrap*

Licensing issues
The AS Java does not have a valid license. Either the license has never been installed or the license has expired.

Refer to the Java Server Troubleshooting guide at SDN (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28JSTTSG%29Main+Page) for additional advice to install a valid license

If the issue still persists even after above troubleshooting steps, please open a message for the BC-JAS-SF component and attach a compressed archive containing all files from the /usr/sap/<SID>/<instance>/work directory.

 

Leave a Reply

Your email address will not be published. Required fields are marked *