IBM Support

PM82011: A CANNOTINSTANTIATEOBJECTEXCEPTION OCCURS WHILE PERFORMING A JNDI LOOKUP OF AN EJB INTERFACE.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The JNDI lookup fails with a NameNotFoundException indicating
    the binding names for EJBs in a started application have been
    unexpectedly removed from the namespace.
    

Local fix

  • The wlm_maximumSRCount=x and wlm_minimumSRCount=y variables
    control the maximum and minimum number of servants. If you have
    a maximum servant count larger than the minimum count, change
    the wlm_maximumSRcount variable to have the same value as
    wlm_minimumSRcount. The server's current values for these
    variables are printed in the JES JOB Messages. To modify these
    variables you can use the administrative console.
    .
    In the administrative console, click Servers > Server Types >
      WebSphere application servers > Your_server >
      Java and Process Management >Server Instance
    .
    Then, update the value for Maximum Number of Instances to equal
    Minimum Number of Instances
    .
    save + sync + restart the server
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 for z/OS                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: A CannotInstantiateObjectException      *
    *                      may occur when looking up an EJB in     *
    *                      an application started over multiple    *
    *                      servants.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using multiple servants, the application server
    unexpectedly removes EJB bindings from the namespace for
    applications hosted by a servant that is stopped. The
    applications are still started, however, and their EJB bindings
    must remain in the namespace for lookup within the active
    servants. When the bindings are unexpectedly removed,
    applications in the active servants will fail with the
    exception shown below while attemting to lookup their names.
    com.ibm.websphere.naming.CannotInstantiateObjectException: A
    NameNotFoundException
    occurred on an indirect lookup on the name java:c
    omp/env/ejb/itemBMPjdbcEntityHome. The name
    java:comp/env/ejb/itemBMPjdbcEntityHome
    maps to a JNDI name in deployment descriptor bin
    dings for the application performing the JNDI lookup. Make
    sure that the JNDI name
    mapping in the deployment descriptor binding is c
    orrect. If the JNDI name mapping is correct, make sure the
    target resource can be
    resolved with the specified name relative to the d
    efault initial context.  [Root exception is
    javax.naming.NameNotFoundException:
    Context: S1EMCLG1/clusters/WSAT2, name: ejb/itemBMP1
    3jdbc/ItemBMPjdbcEntityHome: First component in name
    ItemBMPjdbcEntityHome not
    found. [Root exception is org.omg.CosNaming.NamingCon
    textPackage.NotFound:
    IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]]
    at
    com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE
    xt(Helpers.java:1
    081)
    at
    com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectFor
    Lookup(UrlContext
    Helper.java:181)
    at
    com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForL
    ookup(javaURLCont
    extRoot.java:850)
    at
    com.ibm.ws.naming.urlbase.UrlContextImpl.lookupExt(UrlContextImp
    l.java:1454)
    at
    com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLConte
    xtImpl.java:477)
    at
    com.ibm.ws.naming.java.javaURLContextRoot.lookupExt(javaURLConte
    xtRoot.java:485)
    at
    com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContex
    tR
    oot.java:370)
    at
    org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.jav
    a:161)
    at javax.naming.InitialContext.lookup(InitialContext.java:431)
    

Problem conclusion

  • Code has been modified to prevent a stopping servant from
    removing the JNDI binding names of EJBs witin a multi-servant
    environment.
    
    APAR PM82011 is currently targeted for inclusion in Fix Pack
    7.0.0.33 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

  • The wlm_maximumSRCount=x and wlm_minimumSRCount=y variables
    control the maximum and minimum number of servants. If you have
    a maximum servant count larger than the minimum count, change
    the wlm_maximumSRcount variable to have the same value as
    wlm_minimumSRcount. The server's current values for these
    variables are printed in the JES JOB Messages. To modify these
    variables you can use the administrative console.
    .
    In the administrative console, click Servers > Server Types >
      WebSphere application servers > Your_server >
      Java and Process Management > Process Definition > Servant >
      Additional Properties > Environment Entries >
      Click the_variable_you_need_to_change >
      update the value in the Value box >
      save + sync + restart the server.
    

Comments

APAR Information

  • APAR number

    PM82011

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-04

  • Closed date

    2014-01-17

  • Last modified date

    2014-07-01

  • APAR is sysrouted FROM one or more of the following:

    PM48922

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UI18561

       UP14/06/21 P F406

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM82011

Modified date: 01 July 2014