Instruction manuals


of 5
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
  15.09.2012Page 1 of 5  SAP Note 1316652 -Analysis of startup errors for the ASJava 7.10  Note Language: EnglishVersion: 6 Validity: Valid Since 26.01.2011 Summary Symptom  A problem occurs when you start the Application Server Java (AS Java, oldname J2EE Engine ) 7.10 (or newer), and a trace file from the startupframework references this note for further analysis. Other terms jstart JEE J2EE Engine AS Java Reason and Prerequisites The start of an AS Java uses functionality from various SAP Supportcomponents. This note should help you to identify the appropriate componentto ensure that you receive support more quickly. SolutionJava VM detection issues The AS Java is not able to start due to trouble while detecting theproperties 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 RuntimeEnvironment (JRE), because the AS Java needs the Java compiler duringruntime to compile the JSPs and EJB stubs.oCheck that you have installed a suitable Java environment in thelocation defined in the instance profile by the jstart/vm/home or jstartup/vm/home parameter. If neither of these parameters isset, check the JAVA_HOME environment value.oCheck if there are multiple Java versions installed; make sure thatthe JEE Engine uses an appropriate version.oOn 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 workdirectory of the instance. This file can be safely deleted if it containsinaccurate information (e.g. a wrong path).If you experience problems with the Java VM detection, open a message forthe BC-JAS-SF component and attach a compressed archive containing allfiles from the /usr/sap/<SID>/<instance>/work directory. Java VM shared library issues Check that the *.jvm file contains correct information - if not, delete thefile.oIn Windows systems, error code 193 indicates that the Java VM DLLhas a different word length (32 or 64 bit) that the JStart program.In this case, the trace file contains the following error entry:  15.09.2012Page 2 of 5  SAP Note 1316652 -Analysis of startup errors for the ASJava 7.10 *** ERROR => DlLoadLib: LoadLibrary(jvm.dll) Error 193 oUNIX 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.If you experience problems with the Java VM detection or with the Java VMshared library, open a message for the BC-JAS-SF component and attach acompressed archive containing all files from the/usr/sap/<SID>/<instance>/work directory. Java VM initialization issues Problems with initializing the VM are often caused by incorrect parametersin the VM. For more detailed information, refer to the dev_<node> tracefile (for example, dev_server0) or std_<node>.out trace file (for example,std_server0.out).Examples of incorrect parameters:oUnknown parameters, e.g. -XX:someParam  , result in the followingerror message: Command-line option unrecognised: -XX:someParam  Refer to the Java VM documentation for supported parameters andtheir Syntax.o32-bit platforms only: The defined heap is too big; there is notenough contiguous virtual address space to allocate the heap. As aresult, 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 configurationdatabase. Restart the AS Java instance afterwards.oOn Windows platforms, you cannot initialize the Java VM if anotherJVM.DLL exists in the %windir%\system32 directory. The errormessage 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 theinstance. The system issues now the following message in thedev_bootstrap trace: load shared library (jvm.dll), hdl <number>, addr <address>using C:\WINDOWS\system32\jvm.dll   15.09.2012Page 3 of 5  SAP Note 1316652 -Analysis of startup errors for the ASJava 7.10 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 The message  Java node '<name>' terminated with exit code <code>. in the dev_bootstrap or dev_deployment trace file tells that the respectivestartup phase failed; they are accompanied by a Failures in the <text>phase message in the dev_jstart trace. Refer to the corresponding sectionbelow.This message in a dev_server<n> file indicates some malfunction at the ASJava level or at some higher level; such issue requires a more detailedanalysis.Please refer Troubleshooting guide to search the exit code and possibleerror cause - the Troubleshooting guide does not contain a solution please open amessage for the BC-JAS-COR component and attach a compressed archivecontaining all files from the /usr/sap/<SID>/<instance>/work directory andthe log files of the affected server node (from/usr/sap/<SID>/<instance>/j2ee/cluster/server<N>/log). Java process issues The message  Java VM crashed. indicates that the Java VM failed for some reason. Typically, the failedserver node is restarted automatically. Nevertheless, information about thecrash shows up in the dev_server<N> trace files and in other filesgenerated by the Java VM. For the SAP JVM, Note 1305395 provides additionaladvice.Helpful Notes: 1305395 - SAP JVM crash: How to identify and what to do Failures in the 'deploying offline components' phase A part of the deployment process failed.Please check note 1550641. If there is not any applicable solution for theproblem, create a message for the BC-JAS-DPL component and attach acompressed archive containing the following files from the/usr/sap/<SID>/<instance>/work directory: dev_jstart*  15.09.2012Page 4 of 5  SAP Note 1316652 -Analysis of startup errors for the ASJava 7.10  dev_deployment* std_deployment.* jvm_deployment.* Failures in the 'synchronizing binaries' phase A part of the start-up synchronization process failed.Please create a message for the BC-JAS-COR component and attach acompressed archive containing the following files from the/usr/sap/<SID>/<instance>/work directory: 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 neverbeen installed or the license has expired.Refer to the Java Server Troubleshooting guide at SDN( foradditional advice to install a valid license. Other issues For other issues that are not covered explicitly above, please open amessage for the BC-JAS-SF component and attach a compressed archivecontaining all files from the /usr/sap/<SID>/<instance>/work directory. Header Data Release Status:Released for CustomerReleased on:26.01.2011 11:33:17Master Language:EnglishPriority:Recommendations/additional infoCategory:Help for error analysisPrimary Component:BC-JAS-SF Startup Framework  Valid Releases Software ComponentReleaseFrom ReleaseToReleaseand Subsequent KRNL32NUC7.107.107.20XKRNL32UC7.107.107.20XKRNL64NUC7.107.107.20X
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks