Fix (APAR):  WAS_Naming_05-20-2003_5.0.1_cumulative_Fix

Status:  Fix

Release:  5.0.1

Operating System:  All

Supersedes Fixes:  WAS_Naming_04-17-2003_5.0.1_cumulative_Fix

CMVC Defect:  PQ74185

Byte size of APAR:  71105

Date: 2003-06-10

Abstract:  Naming cumulative update #2 for WebSphere Application Server 5.0.1

Description/symptom of problem:  - APAR PQ75057: JNDI lookups resolving to EJB homes or any other non-context objects directed to WebSphere version 3.5.x or non-WebSphere servers fail with a NamingException. The text of the NamingException message is "Unexpected exception". Lookups directed to WebSphere servers running on version 4.0.x or above function normally.

- APAR PQ74411: Support for corbaloc and corbaname URL lookup names in the WebSphere JNDI implementation does not set the JNDI initial context factory property value to use the WebSphere initial context factory.  As a result, the current setting for the initial context factory property is used.  If the property value happens to be set to some other initial context factory, incorrect JNDI behavior may result.

- APAR PQ74185: Websphere non-z/OS JNDI clients cannot look up an object on a WebSphere 4.0 z/OS name server if the look up name contains dots.

- 164629 (Internal tracking number -- Not an APAR): Lookup to a WebSphere Application Server V3.5 EJB fails.

- 156970 (Internal tracking number -- Not an APAR): Small memory leak in the JNDI implementation.

- 154127 (Internal tracking number -- Not an APAR): Improve efficiency of initial context operation.

- APAR PQ72263: Custom Properties of the Generic JMS Provider panel are ignored.  This Naming update is used to support an update to the Messaging component. The Messaging update is contained in another jar.

- 163583 (Internal tracking number -- Not an APAR): Newly created context may not be fully narrowed.  When creating a subcontext through the JNDI interface using WebSphere's JNDI service provider, it is possible that the NamingContext object returned from the name server is not fully narrowed to WebSphere's internal extension to the interface, org.omg.CosNaming.NamingContext. The return type of the bind_new_context method is org.omg.CosNaming.NamingContext, and the object may only be narrowed to that degree.  The ORB used for workstation versions of WebSphere will perform the narrowing, but other ORB implementations may not.  So, the JNDI service provider should make sure that it is fully narrowed.  If it is not fully narrowed, some features of WebSphere's JNDI service provider, such as the ability to bind and look up non-CORBA objects, will not be supported.

Directions to apply fix:  NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Fix Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/was/support/

1) Create temporary "fix" directory to store the jar file:
             UNIX: /tmp/WebSphere/fix
          Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix.

5) Restart WebSphere

6) The temp directory may be removed.

Directions to remove fix:  NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS
     ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
          removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.


1) Shutdown WebSphere

2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  1) Shutdown WebSphere

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere

Additional Information: