IBM Support

IJ18032: EC CAN FAIL TO PROCESS/PARSE EVENTS AFTER PATCHING TO 7.3.2 P3 IF YOU HAVE PRE-EXISTING ROUTING RULES CONFIGURED

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 after patching to QRadar 7.3.2
    patch 3, events received by QRadar collector appliances can
    fail to be processed/parsed when an event forwarder or routing
    rule has been configured.
    In these instances, the events are successfully received by the
    collector into the ecs-ec-ingress process, but are not sent to
    the ecs-ec process for parsing.
    The following threadtop command can be run from the command line
    prompt on a QRadar event collector appliance:
    /opt/qradar/support/threadTop.sh -p 7777 -e "ECS Runtime"  -s
    -n 20
    The following response from the above threadtop identifies that
    the QRadar event collector appliance is affected:
    System Time: 31/07/2019 at 14:49:55.637
    "ECS Runtime Thread" Id=67 in TIMED_WAITING (running in native)
        at java.lang.Thread.sleep(Native Method)
        at java.lang.Thread.sleep(Thread.java:942)
        at
    com.q1labs.core.shared.ariel.ArielSearchLite.waitForArielClient(
    ArielSearchLite.java:1001)
        at
    com.q1labs.core.shared.ariel.ArielSearchLite.toQueryParams(Ariel
    SearchLite.java:531)
        at
    com.q1labs.core.shared.ariel.ArielSearchLite.toQueryParams(Ariel
    SearchLite.java:369)
        at
    com.q1labs.core.shared.ariel.ArielSearchLite.toQueryParams(Ariel
    SearchLite.java:363)
        at
    com.q1labs.core.shared.ariel.ArielSearchLite.toQueryParams(Ariel
    SearchLite.java:358)
        at
    com.q1labs.core.shared.ariel.ArielSearchLite.toQueryParams(Ariel
    SearchLite.java:353)
        at
    com.q1labs.core.shared.selectiveforwardingset.SelectiveForwardin
    gSetCache.setQueryFilter(SelectiveForwardingSetCache.java:329)
        at
    com.q1labs.core.shared.selectiveforwardingset.SelectiveForwardin
    gSetCache.loadSearchForm(SelectiveForwardingSetCache.java:311)
        at
    com.q1labs.core.shared.selectiveforwardingset.SelectiveForwardin
    gSetCache.initializeSetCache(SelectiveForwardingSetCache.java:20
    9)
          - locked java.lang.Object@35323b09
        at
    com.q1labs.core.shared.selectiveforwardingset.SelectiveForwardin
    gSetCache.onInit(SelectiveForwardingSetCache.java:120)
        at
    com.q1labs.frameworks.naming.FrameworksNaming.initializeNewCompo
    nent(FrameworksNaming.java:916)
        at
    com.q1labs.frameworks.naming.FrameworksNaming.getApplicationScop
    edComponent(FrameworksNaming.java:897)
          - locked
    com.q1labs.frameworks.naming.FrameworksNaming@1269d08c
        at
    com.q1labs.frameworks.core.FrameworksContext.getSingletonInstanc
    e(FrameworksContext.java:1404)
        at
    com.q1labs.core.shared.selectiveforwardingset.SelectiveForwardin
    gSetCache.getInstance(SelectiveForwardingSetCache.java:83)
          - locked java.lang.Object@d1bed3f
        at
    com.q1labs.sem.selectiveforwarding.SelectiveForwardingCommunicat
    or.onInit(SelectiveForwardingCommunicator.java:95)
        at
    com.q1labs.frameworks.naming.FrameworksNaming.initializeNewCompo
    nent(FrameworksNaming.java:916)
        at
    com.q1labs.frameworks.naming.FrameworksNaming.getApplicationScop
    edComponent(FrameworksNaming.java:897)
          - locked
    com.q1labs.frameworks.naming.FrameworksNaming@1269d08c
        at
    com.q1labs.frameworks.core.FrameworksContext.getSingletonInstanc
    e(FrameworksContext.java:1404)
    

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.3.2 Patch 4.
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ18032

  • 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-07-31

  • Closed date

    2019-08-16

  • Last modified date

    2019-08-16

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

Document Information

Modified date:
16 August 2019