IBM Support

IJ16435: SENSORPROTOCOLSTATUS AND SENSORPROTOCOLSTATUSSENTRY DATABASE TABLES BLOAT AND SOMETIMES CAUSE USER INTERFACE OUTAGES

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 in instances where the
    sensorprotocolstatus and sensorprotocolstatusentry database
    tables bloat in environments where there are a large number of
    bulk added log sources that use sensorprotocolstatus records.
    The bloat can eventually cause a TxSentry to kill the tomcat
    process leading to the QRadar User Interface becoming
    unresponsive until all required processes are running as
    expected.
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occurring:
    [NOT:0000003000][127.0.0.1/- -] [-/- -]Could not execute
    statement UPDATE sensordevice as main SET eps60s =
    COALESCE(temp.eps60s, main.eps60s),timestamp_eps60s =
    COALESCE(temp.timestamp_eps60s,
    main.timestamp_eps60s),peakeps60s = CASE WHEN
    COALESCE(temp.eps60s, main.eps60s) > peakeps60s THEN
    COALESCE(temp.eps60s, main.eps60s) ELSE peakeps60s
    END,timestamp_peakeps60s = CASE WHEN COALESCE(temp.eps60s,
    main.eps60s) > peakeps60s THEN COALESCE(temp.timestamp_eps60s,
    main.timestamp_eps60s) ELSE timestamp_peakeps60s
    END,status_record = COALESCE(temp.status_record,
    main.status_record),timestamp_last_seen =
    COALESCE(temp.timestamp_last_seen, main.timestamp_last_seen)
    FROM temp_sensordevice temp WHERE temp.id = main.id
    [tomcat] [LogSourceServices_PersisterTimer]
    org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR:
    insert or update on table "sensordevice" violates foreign key
    constraint "sensor_device_status_fkey"
    [tomcat] [LogSourceServices_PersisterTimer]    at
    org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(Logg
    ingConnectionDecorator.java:219)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(Logg
    ingConnectionDecorator.java:195)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$10
    00(LoggingConnectionDecorator.java:59)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingCo
    nnection$LoggingPreparedStatement.execute(LoggingConnectionDecor
    ator.java:1230)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.execute(
    DelegatingPreparedStatement.java:367)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.execute(
    DelegatingPreparedStatement.java:367)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedSt
    atement.execute(JDBCStoreManager.java:1792)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.execute(
    DelegatingPreparedStatement.java:367)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.frameworks.session.PreparedStatementWrapper.execute(P
    reparedStatementWrapper.java:240)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceServices$PersistLogSourceUpdateT
    ask.executeStatement(LogSourceServices.java:353)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceServices$PersistLogSourceUpdateT
    ask.persistLogSourceUpdates(LogSourceServices.java:321)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    com.q1labs.rpcservices.LogSourceServices$PersistLogSourceUpdateT
    ask.run(LogSourceServices.java:263)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    java.util.TimerThread.mainLoop(Timer.java:566)
    [tomcat] [LogSourceServices_PersisterTimer]    at
    java.util.TimerThread.run(Timer.java:516)
    

Local fix

  • No workaround available.
    

Problem summary

  • This issue was fixed (moving foward) in QRadar QRM QVM release
    of 7.3.1 Patch 8 Interimfix 03, 7.3.2 Patch 2 Interimfix 01 and
    7.3.2 Patch 3.
    If this issue has been experienced, please contact Support for
    assistance with additional fixes that also need to be applied.
    

Problem conclusion

  • This issue was fixed (moving foward) in QRadar QRM QVM release
    of 7.3.1 Patch 8 Interimfix 03, 7.3.2 Patch 2 Interimfix 01 and
    7.3.2 Patch 3.
    If this issue has been experienced, please contact Support for
    assistance with additional fixes that also need to be applied.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ16435

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    731

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-28

  • Closed date

    2019-07-25

  • Last modified date

    2020-07-10

  • 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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSBQAC","label":"IBM QRadar SIEM"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"731"}]

Document Information

Modified date:
11 July 2020