If the data is indicating a memory leak in native JVM code,
contact the IBM® service team. If the problem is Java™ heap exhaustion, it is much less likely
to be an SDK issue, although it is still possible.
The process for raising a bug is detailed in
Submitting problem reports, and the data
that should be included in the bug report is listed as follows:
- Required:
- The OutOfMemoryCondition. The error itself with any message or
stack trace that accompanied it.
- -verbose:gc output. (Even if the problem is determined
to be native heap exhaustion, it can be useful to see the verbose
gc output.)
- As appropriate:
- The svmon snapshot output
- The Heapdump output
- The javacore.txt file