IBM Support

IV98896: VULNERABILITY SCANS CAN APPEAR TO NEVER COMPLETE AND/OR SOMETIMES TAKE LONGER THAN EXPECTED TO COMPLETE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • It has been observed that vulnerability scans can sometimes
    appear to never complete and/or take longer than expected to
    complete.
    
    These particular instances of long duration scans have been
    attributed to a "build reports" agent process that can cause
    qvmprocessor out of memory occurences.
    
    Messages similar to followign might be visible in
    /var/log/qradar.log when this issue is occurring:
    
    Line 173170: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: Discovered out-of-memory error for
    qvmprocessor process.
        Line 173170: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: Discovered out-of-memory error for
    qvmprocessor process.
        Line 173171: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: Discovered out-of-memory error for
    qvmprocessor process.
        Line 173171: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: Discovered out-of-memory error for
    qvmprocessor process.
        Line 173172: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: out-of-memory TYPE: qvmprocessor,
    PID: 19428.
        Line 173172: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: out-of-memory TYPE: qvmprocessor,
    PID: 19428.
        Line 173173: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: Discovered out-of-memory error for
    qvmprocessor(type: qvmprocessor, pid: 19428).
        Line 173173: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: Discovered out-of-memory error for
    qvmprocessor(type: qvmprocessor, pid: 19428).
        Line 173174: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: out-of-memory TYPE: qvmprocessor,
    PID: 19428.
        Line 173174: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: out-of-memory TYPE: qvmprocessor,
    PID: 19428.
        Line 173175: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: Discovered out-of-memory error for
    qvmprocessor(type: qvmprocessor, pid: 19428).
        Line 173175: Jun  5 00:42:29 <hostname>
    OutOfMemoryMonitor[10929]: Discovered out-of-memory error for
    qvmprocessor(type: qvmprocessor, pid: 19428).
        Line 173184: Jun  5 00:42:37 <hostname>
    qvmprocessor[19428]: Caused by: java.lang.OutOfMemoryError:
    Java heap space
        Line 173203: Jun  5 00:42:45 <hostname>
    qvmprocessor[19428]: ... Exception in thread
    "imqConnectionFlowControl-0" 5java.lang.OutOfMemoryError: Java
    heap space
        Line 173218: Jun  5 00:42:49
    ::ffff:127.0.0.1[qvmprocessor.qvmprocessor]
    [QVM-ResultDispatcher]
    org.springframework.transaction.CannotCreateTransactionException
    : Could not open JDBC Connection for transaction; nested
    exception is java.lang.OutOfMemoryError: Java heap space
        Line 173232: Jun  5 00:42:49
    ::ffff:127.0.0.1[qvmprocessor.qvmprocessor]
    [QVM-ResultDispatcher] java.lang.OutOfMemoryError
        Line 173272: Jun  5 00:42:49
    ::ffff:127.0.0.1[qvmprocessor.qvmprocessor] [qtp821598929-107]
    java.lang.OutOfMemoryError
        Line 173330: Jun  5 00:42:49
    ::ffff:127.0.0.1[qvmprocessor.qvmprocessor] [qtp821598929-107]
    com.q1labs.frameworks.core.ThreadExceptionHandler: [ERROR]
    [NOT:0030003100][127.0.0.1/- -] [-/- -]Out of memory discovered
        Line 173332: Jun  5 00:42:49
    ::ffff:127.0.0.1[qvmprocessor.qvmprocessor]
    [qvmScheduler_Worker-4] java.lang.OutOfMemoryError
        Line 173501: Jun  5 00:42:49
    ::ffff:127.0.0.1[qvmprocessor.qvmprocessor]
    [qvmScheduler_Worker-4] org.quartz.SchedulerException: Job
    threw an unhandled exception. [See nested exception:
    java.lang.OutOfMemoryError: Java heap space]
    

Local fix

  • No workaround available.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.3.2 Patch 3.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.3.2 Patch 3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV98896

  • Reported component name

    QR VULNERABILIT

  • Reported component ID

    5725QVMSW

  • Reported release

    728

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2019-07-25

  • Last modified date

    2019-07-25

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

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

Fix information

  • Fixed component name

    QR VULNERABILIT

  • Fixed component ID

    5725QVMSW

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSHLPS","label":"IBM Security QRadar Vulnerability Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"728","Edition":""}]

Document Information

Modified date:
25 July 2019