IBM Support

PM35743: MULTIPLE THREADS ARE RUNNING IN HASHMAP, WHICH CALLED SECURITYCONFIGIMPL.GETPROPERTYBOOL METHOD CAUSING HIGH CPU

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Multiple threads are running in HashMap, which called
    SecurityConfigImpl.getPropertyBool method causing high CPU
    
    
    3XMTHREADINFO      "WebContainer : 1"
    J9VMThread:0x00000000025E4800,
    j9thread_t:0x0000000011D53950,
    java/lang/Thread:0x000000004257FF18,
    state:CW, prio=5
    3XMTHREADINFO1            (native thread ID:0x3C5E, native
    priority:0x5,
    native policy:UNKNOWN)
    3XMTHREADINFO2            (native stack address range
    from:0x00002AAABD757000, to:0x00002AAABD798000, size:0x41000)
    3XMTHREADINFO3           Java callstack:
    4XESTACKTRACE                at
    java/util/HashMap.rehash(HashMap.java:696(Compiled Code))
    4XESTACKTRACE                at
    java/util/HashMap.rehash(HashMap.java:730(Compiled Code))
    4XESTACKTRACE                at
    java/util/HashMap.putImpl(HashMap.java:626(Compiled Code))
    4XESTACKTRACE                at
    java/util/HashMap.put(HashMap.java:605(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/security/config/SecurityConfigImpl.getPropertyBool(Se
    curityConfigImpl.java:1507)
    
    
    3XMTHREADINFO      "WebContainer : 3"
    J9VMThread:0x00000000025E6800,
    j9thread_t:0x00002AAAC05475A0,
    java/lang/Thread:0x00000000425A7510,
    state:CW,
    prio=5
    3XMTHREADINFO1            (native thread ID:0x3C60, native
    priority:0x5,
    native
    policy:UNKNOWN)
    3XMTHREADINFO2            (native stack address range
    from:0x00002AAABE283000, to:0x00002AAABE2C4000,
    size:0x41000)
    3XMTHREADINFO3           Java callstack:
    4XESTACKTRACE                at
    java/util/HashMap.rehash(HashMap.java:696(Compiled
    Code))
    4XESTACKTRACE                at
    java/util/HashMap.rehash(HashMap.java:730(Compiled
    Code))
    4XESTACKTRACE                at
    java/util/HashMap.putImpl(HashMap.java:626(Compiled
    Code))
    4XESTACKTRACE                at
    java/util/HashMap.put(HashMap.java:605(Compiled
    Code))
    4XESTACKTRACE                at
    com/ibm/ws/security/config/SecurityConfigImpl.getPropertyBool(Se
    curityConfigImpl.java:1507)
    
    After data review, two threads running HashMap code called by
    
    com/ibm/ws/security/config/SecurityConfigImpl.getPropertyBool(Se
    curityConfigImpl.java:1507) are consuming high CPU.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server running with security enabled.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: In certain timing situations between    *
    *                      threads, high CPU utilization can       *
    *                      occur.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Invalid concurrent access to internal HashMap objects can
    result in high CPU utilization under certain timing
    conditions.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM35743

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-28

  • Closed date

    2011-04-29

  • Last modified date

    2011-04-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM35743

Modified date: 29 April 2011