IBM Support

IJ20453: REFERENCE DATA CAN FAIL TO BE UPDATED WHEN REFERENCEDATA.TIMETOLIVE.PERIOD IS SET TO 0

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 in some instances
    referencedata.timetolive.period is set to 0 in
    /opt/qradar/conf/frameworks.properties
    When this issue occurs, a failed reference data manager
    initialization can be experienced causing reference data not to
    be updated.
    This can also affect some app functionality (eg. Reference data
    not being updated by UBA as expected).
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue occurs:
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]
    com.q1labs.core.shared.referencedata.ReferenceDataUpdateServiceT
    hread: [ERROR] [NOT:0000003000][xxxxx/- -] [-/-
    -]ReferenceDataUpdateServiceThread An unexpected exception was
    encountered processing name=UBA : User Accounts, Successful,
    Recent size=6 {shared:[host/xxxxxxxxxxxxxx]} Jun 11 14:04:59
    ::ffff: [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]
    java.lang.NullPointerException Jun 11 14:04:59 ::ffff:xxxxxxx
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1] at
    com.q1labs.core.shared.referencedata.ReferenceDataUpdateServiceT
    hread.run(ReferenceDataUpdateServiceThread.java:100)
    tomcat[5690]: 11-Jun-2019 14:09:13.428 WARNING [xxxxxx(7157925)
    /console/do/rulewizard]
    com.sun.messaging.jmq.jmsclient.ExceptionHandler.logCaughtExcept
    ion [I500]: Caught JVM Exception: com.s
    un.messaging.jms.JMSException: [ADD_PRODUCER_REPLY(19)]
    [C4036]: A broker error occurred. :[409] [B4183]: Producer can
    not be added to destination ReferenceDataUpdates [Topic], limit
    of 100 producers would be exceeded user=qradar, broker
    =127.0.0.1:7676(7677) Jun 11 14:09:13
    ::ffff:xxxxxxx[tomcat.tomcat] [xxxx@xxxxx (7157925)
    /console/do/rulewizard]
    com.q1labs.core.shared.referencedata.ReferenceDataManager:
    [ERROR] [NOT:0000003000][xxxxxxx/- -] [-/- -]Unable to initiali
    ze Reference Data Manager
    [tomcat.tomcat] [Token: SIRT_Script_access@xxxxx(519)
    /console/restapi/api/reference_data/sets/ThreatIntel_False_Posit
    ives_IP] Caused by:
    Jun 28 08:59:34 ::ffff:xxxxxxx [tomcat.tomcat] [Token:
    SIRT_Script_access@xxxxx(519)
    /console/restapi/api/reference_data/sets/ThreatIntel_False_Posit
    ives_IP] java.lang.IllegalArgumentException: Non-positive
    period.
    [tomcat.tomcat] [Token: SIRT_Script_access@xxxx(519)
    /console/restapi/api/reference_data/sets/ThreatIntel_False_Posit
    ives_IP]    at java.util.Timer.schedule(Timer.java:297)
    [tomcat.tomcat] [Token: SIRT_Script_access@xxxx (519)
    /console/restapi/api/reference_data/sets/ThreatIntel_False_Posit
    ives_IP]    at
    com.q1labs.frameworks.events.timer.TimerEventGenerator.addListen
    er(TimerEventGenerator.java:102)
    [tomcat.tomcat] [Token: SIRT_Script_access@xxxx(519)
    /console/restapi/api/reference_data/sets/ThreatIntel_False_Posit
    ives_IP]    at
    com.q1labs.frameworks.session.SessionContext.addTimerEventListen
    er(SessionContext.java:778)
    [tomcat.tomcat] [Token: SIRT_Script_access@xxxx(519)
    /console/restapi/api/reference_data/sets/ThreatIntel_False_Posit
    ives_IP]    at
    com.q1labs.core.shared.referencedata.ReferenceDataManager.onInit
    (ReferenceDataManager.java:136)
    [tomcat.tomcat] [Token: SIRT_Script_access@xxxx(519)
    /console/restapi/api/reference_data/sets/ThreatIntel_False_Posit
    ives_IP]    at
    com.q1labs.frameworks.naming.FrameworksNaming.initializeNewCompo
    nent(FrameworksNaming.java:916)
    

Local fix

  • Contact Support for a possible workaround that might address
    this issue in some instances.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.4.1 and
    7.3.3 FixPack 5.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.4.1 and
    7.3.3 FixPack 5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ20453

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    732

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-23

  • Closed date

    2020-08-07

  • Last modified date

    2020-10-08

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSBQAC","label":"IBM QRadar SIEM"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"732"}]

Document Information

Modified date:
09 October 2020