Fix (APAR):  JR29799

Status:  Fix

Release:  6.1.2

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  18507

Date: 2008-08-21

Abstract:  Unable to promote stand alone server to cluster member.

Description/symptom of problem:  
JR29799 resolves the following problem:

ERROR DESCRIPTION:?                                             
Failed to lookup ActivationSpec after promoting a standalone    
server to cluster.                                              

LOCAL FIX:?                                                     
None                                                            

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server v6.1.2 Users.

PROBLEM DESCRIPTION:
Unable to promote stand alone server
to cluster member.

RECOMMENDATION:
None

A bug in the Service Component Architecture code was sending
cluster name to retrieve the node scope, instead of the node
name. This caused the node scope variable to return null
causing the following exception:

[5/28/08 6:30:27:438 CDT] 00000021 RALifeCycleMa E
J2CA0052E: The lookup of the ActivationSpec with JNDI Name
manualrecovery failed due to exception javax.naming.
NameNotFoundException: Context: 82Cell1/clusters/PECluster,
name: manualrecovery: First component in name manualrecovery
not found. [Root exception is org.omg.CosNaming.NamingContext
Package.NotFound: IDL:omg.org/CosNaming/NamingContext/
NotFound:1.0]
at com.ibm.ws.naming.jndicos.CNContextImpl.processNot
FoundException(CNContextImpl.java:4730)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup
(CNContextImpl.java:1907)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup
(CNContextImpl.java:1862)

PROBLEM CONCLUSION:?                                            


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. 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) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed

1) Shutdown WebSphere Process Server. 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 Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

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) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: