IBM Support

PM84740: IN JAX-WS WS-SECURITY, WHEN THERE IS AN LTPA TOKEN IN A CALLER CONFIGURATION, A MEMORY LEAK MAY OCCUR.

Fixes are available

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.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.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

  • In JAX-WS WS-Security, when there is an LTPA token in a caller
    configuration, a memory leak may occur.
    
    User is receiving the symptom below:
    
    1,099,188,416 (91%) [168] 18
    com/ibm/ws/security/auth/ContextManagerImpl
                                 0x4485e9b0
    
     612,233,040 (50%) [56] 5 com/ibm/ws/security/auth/AuthCache
    0x4506bf00
      216,879,464 (18%) [48] 1
    java/util/concurrent/ConcurrentHashMap
                               0x65d118f8
    
       216,879,416 (18%) [80] 16 array of
    java/util/concurrent/Concurrent
                                 HashMap$Segment 0x51058520
    
        36,289,640 (3%) [40] 2
    java/util/concurrent/ConcurrentHashMap$
                               Segment 0x510587c8
    
        29,019,752 (2%) [40] 2
    java/util/concurrent/ConcurrentHashMap$
                               Segment 0x510587a0
    
        22,577,520 (1%) [40] 2
    java/util/concurrent/ConcurrentHashMap$
                               Segment 0x51058778
    

Local fix

  • No work around at this time.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  WS-Security enabled JAX-WS web services     *
    *                  applications and LTPA tokens                *
    ****************************************************************
    * PROBLEM DESCRIPTION: When there is an LTPA caller token in   *
    *                      JAX-WS WS-Security, a memory leak may   *
    *                      occur.                                  *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that contains this       *
    *                  APAR.                                       *
    ****************************************************************
    In JAX-WS WS-Security, when there is an LTPA token in a caller
    configuration, a memory leak may occur.  This issue has not
    been observed with other security tokens.
    

Problem conclusion

  • When WS-Security has a caller configuration for a token, both
    the identity obtained from the token and the token itself are
    put on the runAs subject.  The token is also put in the
    authentication cache.
    
    When a token consumer retrieves its token from a SOAP message,
    a copy of the token is made that is detached from the SOAP
    message so that a reference to the SOAP message does not
    follow the token around.  When the LTPA token consumer
    performs this copy, the SOAP message does not detach from the
    copy.  Because of this, when the LTPA token copy is put in the
    authentication cache, an object the size of the original SOAP
    message is put in the cache instead of an object the size of
    the LTPA token.
    
    The WS-Security runtime is updated:
    
    Before the runtime puts the LTPA token in the authentication
    cache, a different method is used to make a copy of the LTPA
    token that successfully detaches the SOAP message.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.29, 8.0.0.7, and the fix pack after 8.5.0.2.
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM84740

  • 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

    2013-03-13

  • Closed date

    2013-03-29

  • Last modified date

    2013-03-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

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM84740

Modified date: 29 March 2013