Fix (APAR): PK15389 Status: Fix Release: 6.0.2.3 Operating System: AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: 323508 Byte size of APAR: 9193 Date: 2005-11-29 Abstract: A server in a cluster failed to start with security enabled. Description/symptom of problem: PK15389 resolves the following problem: ERROR DESCRIPTION: A Server in a cluster failed to start with security enabled. The following error message was displayed: [11/14/05 17:58:54:734 PST] 00000027 ServerUserAct E WACT0001E: The method recover in class com.ibm.ws.activity.UserActivityImpl received an unexpected exception; the exception stack trace follows: org.omg.CORBA.NO_PERMISSION: Trace from server: 298002686 at host qastress3.burlingame.ibm.com >> org.omg.CORBA.NO_PERMISSION: Failed to verify caller subject vmcid: 0x49424000 minor code: 303 completed: No at com.ibm.ws.orbimpl.services.lsd.LocationServiceImpl. register_object_adapters(LocationServiceImpl.java:294) at com.ibm.ws.orb.services.lsd._LocationServiceImplBas e._invoke(_LocationServiceImplBase.java:64) at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHan dler(ServerDelegate.java:610) at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDe legate.java:463) at com.ibm.rmi.iiop.ORB.process(ORB.java:439) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1737) at com.ibm.rmi.iiop.Connection.doWork(Connection.java: 2260) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.j ava:65) at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.jav a:95) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.ja va:1455) << END server: 298002686 at host qastress3.burlingame .ibm.com LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: All WebSphere Application Server users with security enabled PROBLEM DESCRIPTION: A server in a cluster failed to start with security enabled. RECOMMENDATION: None A server in a cluster with security enabled failed to start , and the following error message was displayed: [11/14/05 17:58:54:734 PST] 00000027 ServerUserAct E WACT0001E: The method recover in class com.ibm.ws.activity.UserActivityImpl received an unexpected exception; the exception stack trace follows: org.omg.CORBA.NO_PERMISSION: The problem was caused by the call to method invokeRegisterObjectAdapter in ASServantManager. The constructor needs to call createObjectAdapter using a ContextManager.runAsSystem block in order to establish the proper credentials needed to make the call. PROBLEM CONCLUSION: Class ASServantManager has been changed to invoke the calling code to run in a PrivilegedExceptionAction and called from runAsSystem. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.7 Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 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: