IBM Support

IJ21674: QRADAR 'DEPLOY' FUNCTIONS CAN FAIL DUE TO INCORRECT DATA IN THE BANDWIDTH_EGRESS_FILTER DATABASE TABLE

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

  • "Deploy" functions within QRadar can fail when the bandwidth
    manager global transformer errors out while attempting to
    validate the bandwidth configuration on a host that is not a
    part of the QRadar deployment.
    This can occur after a configuration restore has been performed.
    Messages similar to the following might be visible in QRadar
    logging when this issue occurs:
    com.q1labs.frameworks.exceptions.FrameworksException: Failed to
    get next filter ID for hostID=677 and wildcard device
      at
    com.q1labs.core.shared.bm.BandwidthConfigurationUtilities.update
    BMForAQSDeployment(BandwidthConfigurationUtilities.java:155)
      at
    com.q1labs.configservices.config.globalset.ibm.BandwidthManagerT
    ransformer.updateDeploymentAQSConfig(BandwidthManagerTransformer
    .java:110)
      ... 80 more
    Caused by:
    com.q1labs.frameworks.exceptions.FrameworksException: Failed to
    execute query for next valid class ID
      at
    com.q1labs.core.shared.bm.BandwidthConfigurationUtilities.getNex
    tValidFilterID(BandwidthConfigurationUtilities.java:942)
      at
    com.q1labs.core.shared.bm.BandwidthConfigurationUtilities.update
    BMForAQSDeployment(BandwidthConfigurationUtilities.java:151)
      ... 81 more
    Caused by:
    <openjpa-2.4.3-r422266:1833086 nonfatal user error>
    org.apache.openjpa.persistence.ArgumentException: Cannot load
    object with id
    "com.q1labs.core.dao.bm.BandwidthEgressFilter-com.q1labs.
    core.dao.bm.BandwidthEgressFilterCompKey@b055f". Instance
    "com.q1labs.core.dao.bm.BandwidthEgressFilter@31a91e2c" with
    the same id already exists in the L1 cache. This can occur when
    you assign an existing id to a new instance, and before
    flushing attempt to load the existing instance for that id.
    

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.2 FixPack
    3 and 7.3.3 FixPack 8.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.4.2 FixPack
    3 and 7.3.3 FixPack 8.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ21674

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    730

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-12-16

  • Closed date

    2021-04-12

  • Last modified date

    2021-05-03

  • 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":"730"}]

Document Information

Modified date:
04 May 2021