Closed as program error.
Error Message: java.lang.OutOfMemoryError: Failed to create a thread: . Stack Trace: N/A .
There are two possible workarounds: 1) Reduce the maximum size of heap by using -Xmx option 2) Reduce the maximum size of JIT scratch memory by using -Xjit=scratchSpaceLimit=<nnn>
This issue shows mainly on platforms with limited virtual memory available to applications. For instance, on Windows 32bit, by default applications have a virtual address space of 2GB (the remaining 2GB is used by kernel). Java heap, VM data structures, classes, JIT data structures, etc. need to fit in this relatively small space. It is possible that at some point the application will exhaust this space, no thread can be created and therefore the application will terminate with the OutOfMemory message
This defect will be fixed in: 6.0.1 GA FP2 . The JIT has been changed to monitor the remaining virtual memory space available to applications and reduce the amount of memory needed for compilations when remaining memory space is under a certain threshold. The compilations that need more memory than the threshold will be aborted which may affect performance. . To obtain the fix: Install build 20110517 or later
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels