Example error message:\n
\n
2010-07-09 16:42:41,654 ERROR (PerfERDC:137) - service Platform Performance Gatherer (192) on host DKLBMMDB1 (34) Error getting data from agent: Java heap space Throwable: java.lang.OutOfMemoryError.\n
\n
Generally this error indicates that one of the internal up.time JVM memory pools has been saturated. In most cases this is the JAVA_HEAP space. There are several reasons this could occur:\n
\n
1) The OS hosting up.time has run out of memory.\n
2) A long running report has consumed all of the available HEAP.\n
3) Other up.time jobs/tasks have consumed available HEAP.\n
\n
If the up.time java process terminated as a result of this error, you will likely find a file named hs_err* in the up.time install directory that contains more information about why the JVM failed.\n
\n
Please contact uptime Support to troubleshoot this issue further.
\n
2010-07-09 16:42:41,654 ERROR (PerfERDC:137) - service Platform Performance Gatherer (192) on host DKLBMMDB1 (34) Error getting data from agent: Java heap space Throwable: java.lang.OutOfMemoryError.\n
\n
Generally this error indicates that one of the internal up.time JVM memory pools has been saturated. In most cases this is the JAVA_HEAP space. There are several reasons this could occur:\n
\n
1) The OS hosting up.time has run out of memory.\n
2) A long running report has consumed all of the available HEAP.\n
3) Other up.time jobs/tasks have consumed available HEAP.\n
\n
If the up.time java process terminated as a result of this error, you will likely find a file named hs_err* in the up.time install directory that contains more information about why the JVM failed.\n
\n
Please contact uptime Support to troubleshoot this issue further.