IBM Support

PK99859: SESSION TIMEOUT ON A THREAD RESULTS IN NAMENOTFOUNDEXCEPTION.

Fixes are available

7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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

  • WebSphere Application Server [BASE edition, 7.0.0.5]
    
    When a Session Object times out due to the timeout property and
    a new Initial Context followed by a lookup is done the following
    exception is encountered. This is due to the
    WsSessionInvalidator Object creating a new thread that is not
    associated with the J2EE application:
    
    ----------------------------------------------------------------
    javax.naming.ConfigurationException [Root exception is
    javax.naming.NameNotFoundException: Name comp/env/service not
    found in context "java:".]
    at
    com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExce
    ptionWithDefaultJavaNS(javaURLContextImpl.java:420)
    at
    com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextI
    mpl.java:398)
    at
    com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextR
    oot.java:214)
    at
    com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextR
    oot.java:154)
    at javax.naming.InitialContext.lookup(InitialContext.java:450)
    at
    test.listeners.SampleSessionListener.getSampleService(SampleSess
    ionListener.java:48)
    at
    test.listeners.SampleSessionListener.sessionDestroyed(SampleSess
    ionListener.java:39)
    at
    com.ibm.ws.session.http.HttpSessionObserver.sessionDestroyed(Htt
    pSessionObserver.java:177)
    at
    com.ibm.ws.session.SessionEventDispatcher.sessionDestroyed(Sessi
    onEventDispatcher.java:160)
    at
    com.ibm.ws.session.StoreCallback.sessionInvalidated(StoreCallbac
    k.java:126)
    at
    com.ibm.ws.session.store.memory.MemorySession.invalidate(MemoryS
    ession.java:222)
    at
    com.ibm.ws.session.store.memory.MemoryStore.runInvalidation(Memo
    ryStore.java:399)
    at
    com.ibm.ws.session.WsSessionInvalidator.alarm(WsSessionInvalidat
    or.java:64)
    at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:127)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:155
    ----------------------------------------------------------------
    
    The above error does not occur when calling the Session Object's
    invalidate() method.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server customers  *
    *                  on version 7 who have defined http session  *
    *                  listeners that access resources within the  *
    *                  web module context.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: An exception is thrown during           *
    *                      invalidation processing by session      *
    *                      manager.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem occurs under the following conditions:
    1. If no session persistence is configured, and
    2. Session listeners have been defined, and
    3. Session listener processing accesses resources in the web
    module such as naming lookups or loading of classes.
    
    During invalidation a ClassNotFoundException or
    NameNotFoundException exception can be thrown when the
    listener is fired.
    

Problem conclusion

  • Code changes have been made to the session manager to set the
    context correctly during invalidation processing. This APAR is
    not applicable to versions prior to V7.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.l1.  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

    PK99859

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-28

  • Closed date

    2010-01-26

  • Last modified date

    2010-01-26

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021