IBM Support

IJ25352: QRADAR CUSTOM RULE ENGINE CAN EXPERIENCE PERFORMANCE DEGRADATION WHEN USING X-FORCE RULES

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

  • The QRadar custom rule engine (CRE) can experience performance
    degradation when X-Force rules are in use.
    When this occurs, System Notification messages similar to
    'Performance degradation has been detected in the event
    pipeline. Event(s) were routed directly to storage' can
    sometimes be observed if the CRE can no longer keep up with the
    processing of events due.
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occurring:
    [ecs-ep.ecs-ep] [CRE Processor [5]]
    java.nio.BufferUnderflowException
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    java.nio.DirectByteBuffer.get(DirectByteBuffer.java:271)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    java.nio.ByteBuffer.get(ByteBuffer.java:715)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.GenericSerializer.objectFromByteBuff
    er(GenericSerializer.java:33)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.GenericSerializer.get(GenericSeriali
    zer.java:74)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.GenericSerializer.get(GenericSeriali
    zer.java:17)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.ChainAppendCache$InsertionChainEntry
    .deserialize(ChainAppendCache.java:320)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.ChainAppendCache$ChainEntry.read(Cha
    inAppendCache.java:241)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.ChainAppendCache.readChainEntry(Chai
    nAppendCache.java:1211)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.ChainAppendCache.findOnDisk(ChainApp
    endCache.java:1162)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.ChainAppendCache.findOnDisk(ChainApp
    endCache.java:1148)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.frameworks.cache.ChainAppendCache.get(ChainAppendCach
    e.java:1000)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.core.aql.XForceFunctions.getCategorization(XForceFunc
    tions.java:278)
    [ecs-ep.ecs-ep] [CRE Processor [5]]    at
    com.q1labs.core.aql.XForceManager.getCategorization(XForceManage
    r.java:268)
    AND
    [ecs-ep.ecs-ep] [CRE Processor [0]]
    java.lang.NegativeArraySizeException
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.GenericSerializer.objectFromByteBuff
    er(GenericSerializer.java:32)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.GenericSerializer.get(GenericSeriali
    zer.java:74)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.GenericSerializer.get(GenericSeriali
    zer.java:17)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.ChainAppendCache$InsertionChainEntry
    .deserialize(ChainAppendCache.java:320)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.ChainAppendCache$ChainEntry.read(Cha
    inAppendCache.java:241)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.ChainAppendCache.readChainEntry(Chai
    nAppendCache.java:1211)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.ChainAppendCache.findOnDisk(ChainApp
    endCache.java:1162)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.ChainAppendCache.findOnDisk(ChainApp
    endCache.java:1148)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.frameworks.cache.ChainAppendCache.get(ChainAppendCach
    e.java:1000)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.core.aql.XForceFunctions.getCategorization(XForceFunc
    tions.java:278)
    [ecs-ep.ecs-ep] [CRE Processor [0]]    at
    com.q1labs.core.aql.XForceManager.getCategorization(XForceManage
    r.java:268)
    

Local fix

  • No workaround available.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.4.1 FixPack
    2.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.4.1 FixPack
    2.
    

Temporary fix

  • 
    

Comments

  • 
    

APAR Information

  • APAR number

    IJ25352

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    733

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-03

  • Closed date

    2020-11-16

  • Last modified date

    2020-11-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

[{"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":"733"}]

Document Information

Modified date:
14 December 2020