Fix (APAR):  PK99108

Status:  Fix

Release:  6.1.1,6.1.0.5

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  PK78206;PK85798;PK89598;PK92660;PK96341;PK96484

CMVC Defect:  xxxxxx

Byte size of APAR:  544362

Date: 2009-10-29

Abstract:  RuntimeErrorException or MalFormedObjectNameException errors can occur when a rollout of a new edition is performed.

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

ERROR DESCRIPTION:                                              
Rollout of new edition of application fails                     
                                                                
Any one of the following two exceptions are noted in the FFDC   
logs                                                            
1)"javax.management.RuntimeErrorException: Error                
occured in RequiredModelMBean while trying to invoke operation  
rolloutEdition" with cause being a                              
"java.lang.IllegalAccessError"                                  
                                                                
2) javax.management.MalformedObjectNameException:               
Invalid character ':' in value part of property                 
 at javax.management.ObjectName.construct(ObjectName.java:529)  
 at javax.management.ObjectName.<init>(ObjectName.java:1314)    
 at                                                             
com.ibm.ws.xd.appeditionmgr.model.ModelFactory.getAppDeploymentT
arget(ModelFactory.java:44)                                     
 at                                                             
com.ibm.ws.xd.appeditionmgr.AppEditionHelper.getEJBTargets(AppEd
itionHelper.java:704)                                           

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
 Users of WebSphere Virtual Enterprise
Version 6.1.0.5 or later

PROBLEM DESCRIPTION:
RuntimeErrorException or
MalFormedObjectNameException errors
can occur when a rollout of a new
edition is performed.

RECOMMENDATION:
None

A RuntimeErrorException error is displayed because of an
IllegalAccessorError error, or a MalformedObjectNameException
error is displayed when a rollout is performed.

The errors occur due to an incompatibility issue between the
StringBuilder APIs on IBM Java Runtime Environment (JRE) 5.0
SR2 and Sun Java Development Kit (JDK) 5.0.

PROBLEM CONCLUSION:                                             
The incompatible API call for the StringBuilder has been        
replaced with compatible API calls.                             


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.1.0-WS-WXDOP-IFPK99108.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.1.0-WS-WXDOP-IFPK99108.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.1.0-WS-WXDOP-IFPK99108.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:  The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.1.2.