IBM Support

IJ07456: EVENT DATA FROM SPILLOVER QUEUE CAN SOMETIMES FAIL TO PARSE WHEN PROCESSED BY THE REGULAR QRADAR PIPELINE

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, event data
    initially processed into QRadar's spillover queue cannot be
    parsed when it is brought through the final QRadar pipeline
    process as it is too large.  Inbound event collection can
    sometimes fail when this issue is occurring.
    
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occurring:
    
    [ecs-ec-ingress.ecs-ec-ingress] [StreamProcessorThread]
    com.q1labs.frameworks.nio.network.StreamProcessor: [ERROR]
    [NOT:0000003000][<ip>/- -] [-/- -]Cannot get the event from
    SpilloverQueue
    [ecs-ec-ingress.ecs-ec-ingress] [StreamProcessorThread]
    com.q1labs.frameworks.nio.exceptions.MessageSizeException:
    Message size exceeds communication buffer capacity 13311990
    [ecs-ec-ingress.ecs-ec-ingress] [StreamProcessorThread]    at
    com.q1labs.frameworks.nio.network.protocol.CollectionHandler.put
    (CollectionHandler.java:47)
    [ecs-ec-ingress.ecs-ec-ingress] [StreamProcessorThread]    at
    com.q1labs.semsources.destinations.SECStoreForwardDestination.se
    ndEventFromQ(SECStoreForwardDestination.java:281)
    [ecs-ec-ingress.ecs-ec-ingress] [StreamProcessorThread]    at
    com.q1labs.frameworks.nio.network.StreamProcessor.sendMessage(St
    reamProcessor.java:96)
    [ecs-ec-ingress.ecs-ec-ingress] [StreamProcessorThread]    at
    com.q1labs.frameworks.nio.network.StreamProcessor.run(StreamProc
    essor.java:55)
    [ecs-ec-ingress.ecs-ec-ingress] [StreamProcessorThread]    at
    java.lang.Thread.run(Thread.java:811)
    

Local fix

  • No workaround available.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 731 patch 5
    interimfix 01 and 731 patch 6.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 731 patch 5
    interimfix 01 and 731 patch 6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ07456

  • 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

    2018-06-29

  • Closed date

    2018-09-18

  • Last modified date

    2018-09-18

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

Document Information

Modified date:
18 September 2018