Fix (APAR):                PK15389

Status:                    Fix

Product:                   WASBOBCAT

Release:                   6.0.2.3,6.0.2.5

Operating System:          All operating systems

Supersedes Fixes:          

Pre-requisite Fixes:       

Exclusive-requisite Fixes: 

CMVC Defect:               PK15389

Byte size of APAR:         9193

Date:                      2005-11-17

Abstract:                  SVT601:Server in cluster failed to start with security enabled.

Description/symptom of problem:
External behaviour experienced.
-------------------------------
An Application Server in a cluster failed to start with security enabled.
Build on which this problem occurred.
---------------------------------------
Product: IBM WebSphere Application Server
Edition: Network Deployment
Package: WebSphere Application Server
Version: 6.0.2.3
Build date: 2005-10-25
Build Number: o0543.32.linux
Steps to reproduce.
-------------------
1. Install WPS
2. Create DMGR profile
3. Create Custom profile
4. Create Cluster (3 cluster members)
5. Condition Cluster for default destination location
6. Install BP and HT Containers on the Cluster
Exceptions the user will see.
-----------------------------
In the SystemOut.log of the server which failed...
[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._LocationServiceImplBase._invoke(_LocationServiceImplBase.java:64)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:610)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.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.java:65)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1455)
<<  END server: 298002686 at host qastress3.burlingame.ibm.com

Directions to apply fix:

  Fix applies to Editions:
    Release 6.0
    X_ Application Server (Express of Base)
    __ Network Deployment  (ND)
    __ WebSphere Business Inegration Server Foundattion (WBISF)
    __ Edge Components
    __ Developer
    __ Extended Deployment (XD)

  Install Fix To:
    Method:
    X_ 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 environment.
       * Be Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
       * Be at V6.0.2.2 or later of the Update Installer. This can be checked by reviewing the level
         of the Update Installer in file <was_root>/updateInstaller/version.txt

  The update Installer can be downloaded from the following link:
       http://www.ibm.com/support/docview.wss?rs=180&uid=swg24008401

  For detailed instructions on how to extract the Update Installer see the following Technote:
       http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006162

  1) Copy PK15389.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.
     It is important that you perform a controlled and complete shutdown of the server to ensure
     that all transactions have completed, before installing the fix.

  3) Launch the Update Installer.

  4) Enter the installation location of the WEebSphere product you want to update.

  5) Select the "Install maintenance package" operation.

  6) Enter the file name of the maintenance package to install (PK15389.pak file which was copied into 
     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 environment.
    * 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.
     It is important that you perform a controlled and complete shutdown of the server to ensure
     that all transactions have completed, before installing the fix.

  2) Launch the Update Installer.

  3) Enter the installation location of the WEebSphere product you want to remove the fix.

  4) Select the "Uninstall maintenance package" operation.

  5) Enter the file name of the maintenance package to uninstall (PK15389.pak).

  6) Uninstall the maintenance package.

  7) Restart WebSphere.


Directions to re-apply fix:

  1) Shutdown WebSphere. 
     It is important that you perform a controlled and complete shutdown of the server to ensure
     that all transactions have completed, before installing the fix.

  2) Follow the instructions to apply the fix.

  3) Restart WebSphere.


Additional Information: