Fix (APAR): PK24376 Status: Fix Release: 6.0.2.9,6.0.2.8,6.0.2.7,6.0.2.6,6.0.2.5,6.0.2.4,6.0.2.3,6.0.2.2,6.0.2.11,6.0.2.1,6.0.2 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: PK24376 Byte size of APAR: 22477 Date: 2006-07-25 Abstract: InvalidNameException recieved during startup trying to register WLMServerRequestInterceptor Description/symptom of problem: PK24376 resolves the following problem: ERROR DESCRIPTION: The customer received the following error when the NodeAgent was started: . Trace: 2006/03/27 10:56:27.690 01 t=6A0BF8 c=UNK key=P2 (0300A07A) Description: IIOP Locate Unknown Object from filename: ./bboocomm.cpp at line: 4882 server_name: k001-wast.essen.karstadt.de Trace: 2006/03/27 10:56:27.691 01 t=6A0BF8 c=UNK key=P2 (00000004) Description: Throw CORBA system exception exception id: CORBA::OBJECT_NOT_EXIST minor code: c9c21047 from filename: ./bbooreq.cpp at line: 534 Trace: 2006/03/27 10:56:27.695 01 t=6A0BF8 c=UNK key=P2 (00000006) Description: Throw CORBA user exception exception id: CORBA::ORB::InvalidName from file: ./bbooorb.cpp at line: 1380 java.lang.InstantiationException: org/omg/CORBA/UserException at com.ibm.ws390.orb.ORB.resolve_initial_references_remote_host_n(N ativeMethod) at com.ibm.ws390.orb.ORB.resolve_initial_references_remote_host(Unk nownSource) at com.ibm.ws390.orb.ORB.locateUsingBootstrap(UnknownSource) at com.ibm.ws390.orb.ORB.objectURLToObject(UnknownSource) at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3450) at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_referen ces(InitialReferenceClient.java:176) . The problem was that WLM tried to register the WLMServerRequestInterceptor on startup on z/OS, but that interceptor did not exist. Thus, an InvalidNameException was thrown. Although the error messages were displayed, the NodeAgent, however, was running and working normally. This APAR was opened for WLM to fix the problem by not registering this Interceptor when running on z/OS. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Application Server V6.1.0 for z/OS PROBLEM DESCRIPTION: InvalidNameException recieved during startup trying to register WLMServerRequestInterceptor RECOMMENDATION: None WLM code tries to register the WLMServerRequestInterceptor with the ORB on z/OS, but this interceptor does not exist on Z/OS, so an InvalidNameException is thrown. PROBLEM CONCLUSION: Support was modified to not register the interceptor if running on z/OS. APAR PK24376 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.1 of WebSphere Application Server V6.1.0 for z/OS. Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * 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 Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: