Fix (APAR):  PK92660

Status:  Fix

Release:  6.1.0.5,6.1.0.4

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

Supersedes Fixes:  PK78206, PK85798, PK89598

CMVC Defect:  xxxxxx

Byte size of APAR:  254778

Date: 2009-08-04

Abstract:  A java.lang.IllegalAccessError exception is displayed when an edition is activated.

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

ERROR DESCRIPTION:                                              
When two editions of the same application are installed and     
the second edition is activated, the following error message    
is displayed:                                                   
                                                                
WPVR0004I: Activating edition 2 of application App1.            
                                                                
Furthermore, the edition is not activated and the following     
error message is displayed in the deployment manager logs:      
                                                                
0000009d MBeanHelper E Could not invoke an operation on object: 
WebSphere:name=AppEditionManager,process=dmgr,                  
platform=dynamicproxy,node=vs-Mockup01CellManager01,version=6.1.
0.25,type=AppEditionManager,mbeanIdentifier=AppEditionManager,  
cell=mockup61_0,spec=1.0 because of exception:                  
javax.management.RuntimeErrorException: Error occured in        
RequiredModelMBean while trying to invoke operation             
activateEdition.                                                

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 Users of WebSphere Virtual Enterprise
with APAR PK85798 or PK89598 installed on
the Solaris operating system

PROBLEM DESCRIPTION:
A java.lang.IllegalAccessError
exception is displayed when an
edition is activated.

RECOMMENDATION:
None

APAR PK85798 introduces a packaging error where the fix bundles
Java 1.5 API-based code in a Java 1.4 format. The IBM SDK 1.5
run time allowed the Java 1.5 API class look-up to succeed. On
Solaris operating systems, however, the IBM repackaged Sun JDK
1.5 causes IllegalAccessErrors errors.

PROBLEM CONCLUSION:                                             
A new cumulative interim fix has been provided for the          
application edition component and has been packaged with the    
Java 1.5 format.                                                


Directions to apply fix:  
Install Fix to:
NOTE: Developers -  Place and X next to the proper installation method and remove this note
__ Application Server Nodes
_X_ Deployment Manager Nodes
__ Both

NOTE:
The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
The Fix Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files.

Customers must be at V6.1.0.17 or newer of the Update Installer.  This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

1) Copy 6.1.0.5-WS-WXDOP-IFPK92660.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 (6.1.0.5-WS-WXDOP-IFPK92660.pak file which was copied in the maintenance directory).  The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes 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.

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
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 (6.1.0.5-WS-WXDOP-IFPK92660.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: