IBM Support

PM30762: TOKEN EXPIRED MESSAGE WHEN SERVER ID IS USED FOR ASYNCBEAN

Fixes are available

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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

  • Occasionally following error is logged in the FFDC area when
    the internal server ID is used in AsynchBean.
    
    com.ibm.websphere.security.WSSecurityException: Received
    credential has expired.
    at
    com.ibm.ws.security.auth.ContextManagerImpl.getCallerCredentials
    (ContextManagerImpl.java:776)
    at
    com.ibm.ws.security.core.SecurityContext.getCallerName(SecurityC
    ontext.java:176)
    at
    com.ibm.ws.security.core.SecurityCollaborator.getCallerPrincipal
    (SecurityCollaborator.java:813)
    at
    com.ibm.ejs.container.BeanO.getCallerPrincipal(BeanO.java:837)
    at
    com.ibm.ejs.container.StatelessBeanO.getCallerPrincipal(Stateles
    sBeanO.java:680)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: While processing an AsynchBean,         *
    *                      WSSecurityException is thrown           *
    *                      occasionally.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During deserializing a propagated Subject in AsynchBean
    context, if propagated Subject is an internal server ID, the
    code sets an expiration time which is the same as LTPAToken
    timeout. Also, in this case, the propagated Subject is cached
    to an internal cache.
    However, there is no code to check whether the cached Subject
    is not expired when it is reused.
    As a result, when this condition happens, the
    WSSecurityException is thrown.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM30762

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-01-18

  • Closed date

    2011-02-17

  • Last modified date

    2011-02-17

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021