IBM Support

IJ06125: A REPORT RUNNER OUT OF MEMORY CAN SOMETIMES OCCUR WHILE CREATINGA REPORT WITH PDF FORMAT WITH VERY HIGH LIMITS (65K) RECORDS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as duplicate of another APAR.

Error description

  • It has been identified that creating a report with multiple
    tables, and choosing to save in PDF format with very high
    limits (65K), can cause an out of memory to occur with the
    report runner process.
    
    Messages similar to the following might be visible in
    /var/log/qradar.error when this issue is occurring:
    
    [report_runner]: JVMDUMP039I Processing dump event "systhrow",
    detail "java/lang/OutOfMemoryError" at 2018/04/17 14:35:21 -
    please wait.
    OutOfMemoryMonitor[22861]: Discovered out-of-memory error for
    report_runner process.
    [report_runner]: JVMDUMP032I JVM requested System dump using
    '/store/jheap/report_runner.report_runner/report_runner.report_r
    unner.system.dmp' in response to an event
    OutOfMemoryMonitor[22861]: Discovered out-of-memory error for
    report_runner process.
    [report_runner]: JVMDUMP030E Cannot write dump to file
    /store/jheap/report_runner.report_runner/report_runner.report_ru
    nner.system.dmp: File exists
    [report_runner]: JVMDUMP013I Processed dump event "systhrow",
    detail "java/lang/OutOfMemoryError".
    [report_runner]: JVMDUMP030E Cannot write dump to file
    /store/jheap/report_runner.report_runner/report_runner.report_ru
    nner.javacore.dmp: File exists
    [report_runner]: JVMDUMP013I Processed dump event "systhrow",
    detail "java/lang/OutOfMemoryError".
    OutOfMemoryMonitor[22861]: out-of-memory TYPE: , PID: .
    OutOfMemoryMonitor[22861]: Discovered out-of-memory error for
    report_runner(type: , pid: ).
    OutOfMemoryMonitor[22861]: Processed out-of-memory error for
    report_runner.
    OutOfMemoryMonitor[22861]: out-of-memory TYPE: , PID: .
    OutOfMemoryMonitor[22861]: Discovered out-of-memory error for
    report_runner(type: , pid: ).
    OutOfMemoryMonitor[22861]: Processed out-of-memory error for
    report_runner.
    [report_runner] [imqConnectionFlowControl-0]
    com.q1labs.frameworks.core.ThreadExceptionHandler: [ERROR]
    [NOT:0000003000][127.0.0.1/- -] [-/- -]Exception was uncaught
    in thread: imqConnectionFlowControl-0
    [report_runner] [imqConnectionFlowControl-0]
    java.lang.OutOfMemoryError
    [report_runner] [imqConnectionFlowControl-0] :
    [report_runner] [imqConnectionFlowControl-0] Java heap space
    [report_runner] [imqConnectionFlowControl-0]    at
    [report_runner] [imqConnectionFlowControl-0]
    com.sun.messaging.jmq.jmsclient.ProtocolHandler
    [report_runner] [imqConnectionFlowControl-0] .
    [report_runner] [imqConnectionFlowControl-0] ping
    [report_runner] [imqConnectionFlowControl-0] (
    [report_runner] [imqConnectionFlowControl-0]
    ProtocolHandler.java
    

Local fix

  • Reduce the limit search and on the tables so that less records
    are returned.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • This APAR is a duplicate of IJ06862
    

APAR Information

  • APAR number

    IJ06125

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    731

  • Status

    CLOSED DUB

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-02

  • Closed date

    2018-06-18

  • Last modified date

    2018-10-24

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"731","Edition":""}]

Document Information

Modified date:
24 October 2018