IV90015: LARGE EXPORT TO EXCEL CAUSES OUT OF MEMORY

3.5.1-TIV-TAP-FP003-WIN
3.5.1-TIV-TAP-FP003-README
3.5.1-TIV-TAP-FP003-LIN
3.5.1-TIV-TAP-FP003-AIX

APAR status

• Closed as fixed if next.

Error description

• Large Export to Excel may cause out of memory crash on the
  JVM/server, or cause a zero byte or seemingly corrupted xlsx
  file.
  When analyzing the heapdump file you will see the following
  classes taking the most of the JVM heap dump space:
  (A)
  "com.tririga.architecture.web.process.useresponse.ExportExcell$2
  ", loaded by "<system class loader>"
  (B) "org.apache.poi.xssf.usermodel.XSSFRichTextString", loaded
  by "<system class loader>"
  

Local fix

• N/A
  

Problem summary

• The Excel integration framework used by the platform needs to
  been upgraded from Apache POI 3.13 to Apache POI 3.15 to take
  advantage of streaming the result set, and not build the entire
  Excel file in memory.
  

Problem conclusion

• The default TRIRIGAWEB property REPORT_MEMORY_USAGE_LIMIT has
  been increased from 35 to 90.
  An issue was resolved where export large excel files from
  report manager would consume the entire java memory heap. This
  has been resolved by streaming the rows written to the excel
  file, and ensuring that TRIRIGA code consumes as little
  resources as possible during the generation of this excel file.
  This is targeted to the 2h2016 and the 3.5.1.3 hot fix.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• 999
  

Fix information

Applicable component levels