Basis Errors and Solutions

Symptom

SAP JVM 6.1 Patch Collection 2 (build 6.1.003)

Solution

The SAP JVM Patch Collection 2 relates to the SAP JVM build 6.1.003.
It contains the following enhancements and corrections:
When parsing XML documents inside JAR archives using the DocumentBuilder.parse(String uri) method, the JAR file was opened from within the parser but never closed. Even using the usual workaround to disable JAR caching, the JAR file was only closed by the garbage collector. With this fix the DocumentBuilder tries to detect URIs specifying XML files in local JAR files. In such cases the JAR files are opened and the parser is run on an InputStream object, not using the provided URI object. After parsing, the JAR file is closed explicitely. If this special handling of local JAR files fails, DocumentBuilder will fall back to the known URI parsing mechanism.Improve Windows memory information provided in hs_error files and other locations for more machines with more than 4 GB main memory. Also virtual memory information is included now.Avoid memory fragmentation when using the Concurrent Mark & Sweep Garbage Collector after “promotion failures” (failed attempts to move Java objects from the Young to the Old Generation).Added new trace in the Concurrent Mark & Sweep Garbage Collector providing information about its indexed free lists (trace option name is -XtraceCMSFreeListSpaceCensus).Limit the size of the Promotion Local Allocation Buffer to 1 MB when the “ParNew” Garbage Collector is used.Avoid SAP JVM crashes with a segmentation violation (SIGSEGV) on Solaris operating systems. In related “hs_err_pid” files or the SAP Application Server Java trace files the following error messages can be found:
SHS: [15056] 12:55:47 ***ERROR (os_solaris.cpp:1024): Creation of VMC mutex failed: Init of mutex failed (error=22).
SHS: [15056] 12:55:47 ***ERROR (jvmEnv.cpp:870): Creation of VMC mutex failed: create_pd failed.
DOD: [15056] 12:55:47 ***ERROR (thread.cpp:1684): Creation of restricted thread lock failed.
# An unexpected error has been detected by SAP Java Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xffffffff77cfc3c8, pid=3614, tid=17766
#
# Java VM: SAP Java Server VM (5.1.036 May 7 2009 18:06:52 – 51_REL – optU – solaris sparc – 6 – bas2:119941 (mixed mode))
# Problematic frame:
# V [libjvm.so+0x1cfc3c8] bool VMCMutex::lock()+0xe0 (sp=0xfffffffe7b7ff560) (pc=0xffffffff77cfc3c8)
The error happens especially in high load situations where many threads are created.Avoid crashes when using VM option “-XX:+DumpStackTraceOnSystemExit”.Improved traces for file open errors with ZIP files.CMS Garbage Collector: Corrected handling of marking stack overflows in the concurrent marking and precleaning phases, thus avoiding heap corruptions. Integrated Sun changeset 6722113.Improved startup time when Java agents are used (e.g. Wily Introscope agents) by allowing JIT compilation for Java agents.HP-UX/IA64: Optimized atomic operations.HP-UX: Change the order for pthread_cond_unlock() and pthread_cond_signal during() calls in the VM’s thread unpark() operation.HP-UX: Generate trace messages for unexpected status after pthread library calls.JIT compiler on HP-UX/PA-RISC: Avoid problems with “branch” instructions with more than 17 bit offset.JIT compiler: Fix crashes in the JIT compiler while performing “loop unrolling” due to inconsistencies in its internal data structures (there were “dead nodes” in a tree representation of the program to be compiled).JIT compiler: Integrate fix for Sun Bug ID 6855164. This avoids crashes in the JIT compiler when it is trying to split a block in its internal data structures representing the program to be compiled.