IBM Support

IJ11493: LOG SOURCE WINDOW CAN TAKE MINUTES TO LOAD DUE TO THREAD LOCK

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 the function of opening the Log
    Source window and/or cancelling the window can sometimes take
    multiple minutes to complete.
    This issue is caused by the decryption of the protocol config
    parameters during the Log Source page loading and in some
    instances a thread lock occurs during the decryption process.
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occurring:
    user@127.0.0.1 (4659) /console/do/core/genericsearchlist"
    Id=311 in RUNNABLE
        at com.ibm.crypto.provider.MD5.a(Unknown Source)
        at com.ibm.crypto.provider.MD5.engineUpdate(Unknown Source)
         - locked com.ibm.crypto.provider.MD5@62d1cd75
        at
    com.ibm.crypto.provider.PBEWithMD5AndTripleDESCipher.engineInit(
    Unknown Source)
        at
    com.ibm.crypto.provider.PBEWithMD5AndTripleDESCipher.engineInit(
    Unknown Source)
        at javax.crypto.Cipher.init(Unknown Source)
        at javax.crypto.Cipher.init(Unknown Source)
        at com.ibm.crypto.provider.I.a(Unknown Source)
        at com.ibm.crypto.provider.JceKeyStore.engineGetKey(Unknown
    Source)
        at java.security.KeyStore.getKey(KeyStore.java:1034)
        at com.ibm.si.mks.TokenKeyStore.get(TokenKeyStore.java:48)
        at com.ibm.si.mks.MasterKeyStore.get(MasterKeyStore.java:56)
        at
    com.ibm.si.mks.KeyStoreCrypto.getKey(KeyStoreCrypto.java:39)
        at
    com.ibm.si.mks.KeyStoreCrypto.decrypt(KeyStoreCrypto.java:70)
        at com.ibm.si.mks.Crypto.decrypt(Crypto.java:52)
        at
    com.q1labs.frameworks.crypto.CryptoUtils.decrypt(CryptoUtils.jav
    a:50)
        at
    com.q1labs.frameworks.core.FrameworksContext.decrypt(FrameworksC
    ontext.java:1148)
        at
    com.q1labs.core.dao.qidmap.SensorProtocolConfigParameters.getVal
    ue(SensorProtocolConfigParameters.java:121)
        at
    com.q1labs.sem.ui.semservices.SensorDeviceForm.copyFromDAO(Senso
    rDeviceForm.java:632)
        at
    com.q1labs.core.ui.util.CopyUtils.copyBeans(CopyUtils.java:90)
        at
    com.q1labs.core.ui.util.CopyUtils.copyToListOfBeans(CopyUtils.ja
    va:59)
    

Local fix

  • Perform Log Source page functions using the QRadar Log Source
    Management app
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.3.1 patch 8
    and 7.3.2 patch 2.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.3.1 patch 8
    and 7.3.2 patch 2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ11493

  • 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-11-22

  • Closed date

    2019-06-03

  • Last modified date

    2019-06-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

[{"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:
03 June 2019