|
Recent changes to the information in the V1.3.1 Diagnostics Guide
These changes are listed in the order in which they became available. The most recent addition is at the bottom.
Path length limitation on Windows SDKs
The Windows v1.3.1 SDK does not support files that have path lengths greater than 255 characters. For more information, see SUNBUG ID: 4403166, which you can see at:  http://developer.java.sun.com/developer/bugParade/bugs/4403166.html.
Changes to dump environment variables
From v1.3.1, from SR6 onwards, the IBM_HEAPDUMP_OUTOFMEMORY and IBM_JAVACORE_OUTOFMEMORY environment variables are enabled by default. Enabling them by default ensures better first failure data capture. When the JVM throws a java.lang.OutOfMemoryError, it will create a javacore file and a heapdump file.
You can disable these defaults by exporting the following two environment variables:
export IBM_HEAPDUMP_OUTOFMEMORY=false
export IBM_JAVACORE_OUTOFMEMORY=false
Additional RAS environment variable
Currently available only on z/OS 31-bit Service Refreshes.
The environment variable ALLOCATION_THRESHOLD=<threshold value> enables a user to identify the java stack of a thread making an allocation request of larger than <threshold value>.
The output is:
Allocation request for <allocation request size> bytes
<Java stack>
if a java stack is available, or
Allocation request for <allocation request size> bytes
No java stack
if there is no java stack.
|
