Troubleshooting
Problem
at com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.common.LogAdapter.handle9416(LogAdapter.java:257)
at com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.common.LogAdapter.handleNls(LogAdapter.java:170)
at com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.common.LogAdapter.onLogEvent(LogAdapter.java:131)
at com.ibm.rmm.util.RmmLogger.baseLog(RmmLogger.java:245)
at com.ibm.rmm.ptl.tchan.transmitter.PacketFireout.run(PacketFireout.java:462)
Caused by: java.lang.OutOfMemoryError: Java heap space
at com.ibm.io.async.AsyncLibrary$IOExceptionCache.get(AsyncLibrary.java:937)
at com.ibm.io.async.AsyncLibrary.getIOException(AsyncLibrary.java:951)
Diagnosing The Problem
Resolving The Problem
In some of the newer Excel emitters, every page break in a report triggers a new worksheet in the Excel file. This only applies to explicit page breaks that the report developer has specified in the report design. Specifically, detail reports (and the detail/subreport template as well as the ad hoc Detail style reports) insert a page break after each record.
Due to the huge number of page breaks in the big report, the emitter would attempt to create same number of sheets.
There's no an actual fix since it is a BIRT component. To avoid this OOM happening, typically use record limits on detail reports since detail reports are often resource-intensive. Or, if this is a custom report, may be able to change the design to reduce the number of page breaks.
Was this topic helpful?
Document Information
Modified date:
16 January 2019
UID
ibm10795592