Basis Errors and Solutions

Symptom

SAP JVM 5.1 Patch Collection 26 (build 5.1.037)

Solution

SAP JVM 5.1 Patch Collection 26 relates to the SAP JVM
build 5.1.037.
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.

Please update the SAP JVM as described in the referenced notes.