15 Jan 2001 Product: WebSphere Advanced Server version 3.0.2.2, (version 3.0.2, PTF 2) APAR PQ45074 E-fix Documentation Problem Description: WLM failover does not proceed correctly. Cause: When the JNDI CosNaming plug-in is called to look up a context, a remote CORBA call on the returned context object is made in a effort to convert the object to its RMI stub object. If a NO_RESPONSE exception is thrown from the call, the plug-in should catch the exception and simply return the unprocessed context object to the caller to allow WLM processing to continue. Instead, the exception is not caught and is passed through to the caller. Contents of this e-fix; PQ45074.jar: Updated class files which belong in the WebSphere library, ujc.jar: com/ibm/ejs/ns/jndi/CNContextImpl.class This e-fix description: readme.txt How to apply fix: You must replace a class file that resides in ujc.jar. Listed below are the steps to update ujc.jar: 1) Stop the Admin Server and all application servers. 2) Save a copy of the original version of ujc.jar, which is found in the directory $WAS_HOME/lib, where $WAS_HOME is the WebSphere AppServer directory. 3) Create a temporary directory, e.g., /tmp/PQ45074 4) Copy PQ45074.jar to the temporary directory. 5) Make the temporary directory your current directory. 6) Extract the contents of PQ45074.jar into the temporary directory, e.g., jar xvf PQ45074.jar Note: If the jar command is not found in your PATH, you can add it to your PATH by running the WebSphere setupCmdLine utility as follows: UNIX: . $WAS_HOME/bin/setupCmdLine.sh WIN: %WAS_HOME%\bin\setupCmdLine.bat where $WAS_HOME (%WAS_HOME%) is the WebSphere AppServer directory. 7) Update ujc.jar with the class file extracted from PQ45074.jar, e.g., jar uvf $WAS_HOME/lib/ujc.jar com/* where $WAS_HOME is the WebSphere AppServer directory. 6) Restart the Admin Server and application servers.