IBM Support

IJ10166: USERS CANNOT LOG INTO QRADAR (USER INTERFACE HANGS) DUE TO THREAD DEADLOCK

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 users can sometimes be unable to
    log into QRadar successfully (User Interface page hangs) due to
    a thread deadlock between UserManager.java, and
    EmbeddedStagingManager.java.
    Messages similar to the following might be visible in QRadar
    logging when this issue is occurring:
    xxxxx@127.0.0.1(7943)
    /console/restapi/api/system/eula_acceptance/163" Id=341 in
    BLOCKED on
    lock=com.q1labs.core.shared.embeddedstaging.EmbeddedStagingManag
    er@xxxxxx
         owned by xxxx@127.0.0.1 (7994)
    /console/JSON-RPC/QRadar.getUndeployedChanges
    QRadar.getUndeployedChanges Id=331
        at
    com.q1labs.core.shared.embeddedstaging.EmbeddedStagingManager.do
    Deploy(EmbeddedStagingManager.java:522)
          - locked
    com.q1labs.core.shared.embeddedstaging.EmbeddedStagingManager@b3
    aabc2
        at
    com.q1labs.core.shared.permissions.UserManager.deployUserById(Us
    erManager.java:982)
          - locked
    com.q1labs.core.shared.permissions.UserManager@37338bf3
        at
    com.ibm.si.eula.api.v9_0.EulaAPI.updateEulaAcceptance(EulaAPI.ja
    va:169)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
        at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:90)
        at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:55)
        at java.lang.reflect.Method.invoke(Method.java:508)
    "xxxxx@127.0.0.1 (7994)
    /console/JSON-RPC/QRadar.getUndeployedChanges
    QRadar.getUndeployedChanges" Id=331 in BLOCKED on
    lock=com.q1labs.core.shared.permissions.UserManager@37338bf3
         owned by xxxxxx@127.0.0.1 (7943)
    /console/restapi/api/system/eula_acceptance/163 Id=341
        at
    com.q1labs.core.shared.permissions.UserManager.getStagedUsers(Us
    erManager.java:571)
          - locked
    com.q1labs.core.shared.permissions.UserManager@37338bf3
        at
    com.q1labs.core.shared.permissions.UserManager.updateConfigurati
    onFile(UserManager.java:829)
        at
    com.q1labs.core.shared.permissions.PermissionsManager.updateConf
    igurationFiles(PermissionsManager.java:569)
          - locked java.lang.Class@5323f3b6
    

Local fix

  • Contact Support to verify the login issue is caused by this
    specific deadlock and if so, a tomcat service restart can be
    performed to correct the deadlock situation.
    

Problem summary

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

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ10166

  • 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-10-05

  • Closed date

    2018-11-29

  • Last modified date

    2018-11-29

  • 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:
29 November 2018