IBM Support

PM30175: NMSV0609W AND CLASSCASTEXCEPTION WERE ISSUED

Fixes are available

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.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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

  • NMSV0609W and ClassCastException were issued if "Access to
    internal server classes" is set to "Restrict"
    
    The customer uses an application which uses TimerManager
    and if "Access to internal server classes" is set to
    "Restrict", the following exceptions can be observed.
    
    1)  NMSV0609W: A Reference object looked up from the context
    xxxCell/nodes/xxxNode01/servers/server1" with the name
    "tm/myTimer" was sent to the JNDI Naming Manager and was
    returned unprocessed.
    Reference data follows:
    Reference Factory Class Name:
    com.ibm.ws.asynchbeans.naming.timer.
    TimerManagerFactory
    Reference Factory Class Location URLs: <null>
    Reference Class Name:
    com.ibm.ws.asynchbeans.timer.TimerManagerImpl
    
    2) java.lang.ClassCastException: javax.naming.Reference
    incompatible with commonj.timers.TimerManager
    [12/9/10 10:35:08:881 JST] 00000018 SystemErr     R
    at com.xxx.xxx.xxx.TimerManagerServlet.init
    
    
    This is not observed when "Access to internal server classes"
    is set to "Allow"
    

Local fix

  • "Access to internal server classes" is set to
    "Allow"
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Users utilizing "RESTRICT" mode class   *
    *                      loading can see class loading failures  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the "Access to internal server classes" option on the
    WebSphere Application Server is set to "RESTRICT", some user
    actions could result in the indirect loading of
    com.ibm.ws.asynchbeans.naming.timer.TimerManagerFactory.  This
    load fails due to the "RESTRICT" setting, despite the customer
    not explicitly loading this class.
    

Problem conclusion

  • The com.ibm.ws.asynchbeans.naming.timer.TimerManagerFactory has
    been added to the exception list, allowing it through the
    "RESTRICT" mode barrier.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.19.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Switching "Access to internal server classes" from "RESTRICT"
    to "ALLOW" solves this issue.
    

Comments

APAR Information

  • APAR number

    PM30175

  • 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-01-11

  • Closed date

    2011-04-04

  • Last modified date

    2011-06-18

  • 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 #: PM30175

Modified date: 18 June 2011