IBM Support

IJ16162: QRADAR USER INTERFACE BECOMES UNRESPONSIVE DURING BULK CHANGES MADE TO A LARGE NUMBER OF LOG SOURCES USING THE API

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 identified that the QRadar User Interface can
    sometimes become unresponsive due to a session leak caused
    during a large amount of bulk changes made to Log Sources using
    the QRadar Log Source Management App (API) in QRadar
    environments with hundreds of thousands of Log Sources.
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occuring:
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]
    com.q1labs.rpcservices.LogSourceServices: [ERROR]
    [NOT:0000003000][10.8.45.14/- -] [-/- -]Unable to get session
    context to update device last seen times
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]
    java.util.ConcurrentModificationException
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    gnu.trove.impl.hash.THashIterator.nextIndex(THashIterator.java:1
    56)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    gnu.trove.impl.hash.THashIterator.hasNext(THashIterator.java:103
    )
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    java.lang.Iterable.forEach(Iterable.java:85)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceUpdate.closePreparedStatements(L
    ogSourceUpdate.java:143)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceServices$PersistLogSourceUpdateT
    ask.persistLogSourceUpdates(LogSourceServices.java:325)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceServices$PersistLogSourceUpdateT
    ask.run(LogSourceServices.java:263)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    java.util.TimerThread.mainLoop(Timer.java:566)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    java.util.TimerThread.run(Timer.java:516)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]
    com.q1labs.frameworks.session.SessionContext: [ERROR]
    [NOT:0000003000][x.x.x.x/- -] [-/- -]28012 leak(s) detected in
    session context: 640ae595-b0db-44fb-a88f-e33fc1a35d32
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]
    com.q1labs.frameworks.session.SessionContext: [ERROR]
    [NOT:0000003000][x.x.x.x/- -] [-/- -]java.sql.PreparedStatement
    leak detected. Object created in following code path
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]
    java.lang.Exception
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.frameworks.session.BaseWrapper.<init>(BaseWrapper.jav
    a:16)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.frameworks.session.PreparedStatementWrapper.<init>(Pr
    eparedStatementWrapper.java:35)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.frameworks.session.ConnectionWrapper.prepareStatement
    (ConnectionWrapper.java:262)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceUpdate.getPreparedStatement(LogS
    ourceUpdate.java:81)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceServices$PersistLogSourceUpdateT
    ask.persistLogSourceUpdates(LogSourceServices.java:312)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceServices$PersistLogSourceUpdateT
    ask.run(LogSourceServices.java:263)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    java.util.TimerThread.mainLoop(Timer.java:566)
    [tomcat.tomcat] [LogSourceServices_PersisterTimer]    at
    java.util.TimerThread.run(Timer.java:516)
    

Local fix

  • No workaround available.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 Patch 1.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 Patch 1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ16162

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    730

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-15

  • Closed date

    2019-12-09

  • Last modified date

    2019-12-09

  • 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

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

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":"730","Edition":""}]

Document Information

Modified date:
09 December 2019