Fix (APAR): PQ79333 Status: Fix Release: 5.0.2.1,5.0.2,5.0.1,5.0.0 Operating System: N/A Supersedes Fixes: CMVC Defect: PQ79333 Byte size of APAR: 6971 Date: 2003-11-25 Abstract: An exception is thrown after the WebSphere 4.0 server group and WebSphere 4.0 admin servers are recycled that the WebSphere 5.0 client is connected to. Description/symptom of problem: When a client application holds onto a WLMable reference (a home object or a remote reference) and all of the WebSphere 4.0 application servers and admin servers are recycled, the client is not able to use any of the references after the application servers and admin servers are available for service again. The WebSphere 5.0 client will receive a 'org.omg.CORBA.NO_IMPLEMENT: minor code: 49421040 completed: No' exception. 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/support/index.html 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: Two custom System properties have to be set for this iFix to work. Here are the instructions for setting the properties. 1. In the admin console, select the "Servers" item on the left side of the console. 2. Under "Servers", select "Application Servers". 3. With all of the application servers displayed, select the application server that is the client application server process that needs to interoperate with the WebSphere Application Server 4.0 application. 4. In the "Additional Properties" section, choose "Process Definition". 5. Inside the "Process Definition" screen under the "Additional Properties" section, choose "Java Virtual Machine". 6. Inside the "Java Virtual Machine" screen under the "Additional Properties" section, choose "Custom Properties". 7. Now 2 custom properties will have to be created. 7a. Create one custom property with the 'name' of com.ibm.websphere.wlm.bootstrap.host and with the 'value' of the name of the WebSphere Application Server 4.0 Bootstrap host. Typically, it will be the same name as the bootstrap host specified for the application client's InitialContext object Provider_URL. 7b. Create a second custom property with the 'name' of com.ibm.websphere.wlm.boostrap.port and with the 'value' of the port of the WebSphere Application Server 4.0 Bootstrap port. Again, typically, it will be the same port value used by the application client's InitialContext object. If this value is not specified, a default value of 900 will be used. Press "Ok" and save/synchronize the changes. Double check to see that the changes have been saved to the client application server process. Also remember that since these are 'System Properties', the client application server process will have to be stopped/restarted for those properties to be loaded by the JVM. You should see the following in the server.xml file for the specific application server.