The output format of a message log indicating insufficient C heap is described below. This format is common for the error report file and standard output.

• In Windows
  

  Exception in thread <ThreadName> java.lang.OutOfMemoryError:requested <n> bytes [ for <message>]. Memory Status ------------- Memory in use: utilization-rate% Physical memory: free-memory-size/total-memory-sizefree Virtual memory: free-memory-size/Total-memory-sizefree Paging file: free-volume/total-volumefree Heap Status ----------- Java-heap-information ----------- Stack Trace ----------- stack-trace Insufficient memory for malloc. JVM generates core file. -----------

• In AIX, HP-UX, or Linux
  

  Exception in thread <ThreadName> java.lang.OutOfMemoryError: requested <n> bytes [for <message>]. Memory Status ------------- maximum size of data segment soft(current) limit: software-limit-value-acquired-by-getrlimit(RLIMIT_DATA) kbytes (Hexadecimal) hard limit: hardware-limit-value-acquired-by-getrlimit(RLIMIT_DATA) kbytes (Hexadecimal) current end of the heap: value-acquired-by-sbrk(0) JVM allocation size by malloc: memory-size-allocated-to-JavaVM kbytes (Hexadecimal) malloc information total space in arena :mallinfo.arena value number of ordinary blocks :mallinfo.ordblks value number of small blocks :mallinfo.smblks value number of holding blocks :mallinfo.hblks value space in holding block headers :mallinfo.hblkhd value space in small blocks in use :mallinfo.usmblks value space in free small blocks :mallinfo.fsmblks value space in ordinary blocks in use :mallinfo.uordblks value space in free ordinary blocks :mallinfo.fordblks value cost of enabling keep option :mallinfo.keepcost value Heap Status ----------- Java-heap-information ----------- Stack Trace ----------- stack-trace -----------

• In Solaris
  

  Exception in thread <ThreadName> java.lang.OutOfMemoryError: requested <n> bytes [for <message>]. Heap Status ----------- Java-heap-information ----------- Stack Trace ----------- stack-trace -----------

When such a message is output, take appropriate measures such as reducing C heap.

The output contents are as follows:

Table 5-27 Output items of message log when C heap is insufficient

If memory becomes insufficient while a message log indicating insufficient C heap is being output, the process cannot be continued. In this case, a simple message in the following format is output to the standard output.

 
java.lang.OutOfMemoryError:requested <n> bytes for <message>
 

The output contents are as follows:

Table 5-28 Output contents of a simple message when the memory is insufficient

After a simple message is output, the Watson log is started and a dump is output. However, in some cases, since the Watson log cannot be output successfully, check the output message for the process results in the standard output.

The following message is output if Watson log startup fails.

 
WatosonLog process generated.But couldn't generate dump file,because of resource shortage.
 

The following message is output if a dump output fails after starting the Watson log.

 
Couldn't generate dump file, because of resource shortage.
 

When these processes are successful, the message shown below is output. However, even in these cases, there are times when the Watson log dump output is not performed successfully. Even when this message is output, confirm whether the dump is actually output.

 
Although Dr.Watson process finished successfully,dump file isn't always generated.
Check your directory where dump file is stored.
 

If the memory is still insufficient when a simple message is output, output of the message and error log file is interrupted and a core dump is generated. When a core dump is generated, the message in the following format is output in the standard output.

 
Can't create logs because of memory shortage.
Insufficient memory for malloc. JVM generates core file