Use the following troubleshooting information
to diagnose and fix problems with the xsLogAnalyzer tool
and its generated reports.
Procedure
- Problem: Out
of memory conditions occur when you
are using the xsLogAnalyzer tool to generate reports.
An example of an error that might occur follows: java.lang.OutOfMemoryError:
GC overhead limit exceeded.
Solution: The
xsLogAnalyzer tool
runs within a Java virtual machine (JVM). You can configure the JVM
to increase the heap size before you run the
xsLogAnalyzer tool
by specifying some settings when you run the tool. Increasing the
heap size enables more event records to be stored in JVM memory.
Start with a setting of 2048M, assuming the operating system has enough
main memory. On the same command-line instance in which you are planning
to run the
xsLogAnalyzer tool, set the maximum
JVM heap size:
java -XmxHEAP_SIZEm
The
HEAP_SIZE value
can be any integer and represents the number of megabytes that are
allocated to JVM heap.
For example, you might
run java -Xmx2048m. If the
out of memory messages continue, or you do not have the resources
to allocate 2048m or more of memory, limit the number of events that
are being held in the heap. You can limit the number of events in
the heap up by passing the -maxRecords parameter
to the .xsLogAnalyzer command
- Problem: When you open a generated report from the xsLogAnalyzer tool,
the browser hangs or does not load the page.
Cause: The
generated HTML files are too large and cannot be loaded by the browser.
These files are large because the scope of the log files that you
are analyzing is too broad.
Solution: Consider using
the -startTime, -endTime,
and -maxRecords parameters when you run the xsLogAnalyzer tool
to restrict the number of log entries that are scanned. Using these
parameters when you run the report makes the reports easier to read
and run more effectively. You can run multiple reports on the same
set of log files.