Fix (APAR): PK69471 Status: Fix Release: 6.0.2.25 Operating System: Windows Supersedes Fixes: CMVC Defect: PK69471 Byte size of APAR: 23949 Date: 2008-08-28 Abstract: When the profile path contains an embedded blank the MBean identifier returned has an invalid object name Description/symptom of problem: PK69471 resolves the following problem: ERROR DESCRIPTION:? PK54440does not work on systems with spaces in the install path namefor example C:\program files\...." LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: All IBM WebSphere Application Server version 6.02.29 users or users with the interim fix for PK54440 installed. PROBLEM DESCRIPTION: When the profile path contains an embedded blank the MBean identifier returned has an invalid object name RECOMMENDATION: None PK54440 which shipped in fixpack 6.0.2.29 attempted to fix the problem: com.ibm.websphere.management.AdminClient#invoke does not work for javax.management.ObjectName objects created with a space in the name string. PK54440 corrected the problem when the space is found in the ObjectName after the profile root. If the space is found before the profile root PK54440 causes the name and mbeanIdentifier attributes in the returned ObjectName to be incorrectly set. After PK54440 is applied: Example 1) If the space is found in the name string after the profile root, the code: String queryObjectNameString ="WebSphere:type=SIBGatewayLink, mbeanIdentifier=cells/myCell/clusters/Spaced Cluster /sib-engines.xml#SIBGatewayLink_1171031578220,*"; ObjectName queryObjectName = new ObjectName(queryObjectNameString); Set objectNameSet = ac.queryNames(queryObjectName, null); will always result in objectNameSet being empty. However,if "Spaced Cluster" is changed to "Spaced%20Cluster" the expected result set is obtained. Example 2) If the space is found in the name string before the profile root, the code: String queryObjectNameString= "WebSphere:type=TransactionService,*" ... results in an ObjectName set containing: "WebSphere:name=/Program Files/IBM/WebSphere/AppServer/profiles/ Dmgr01/config/cells/myCell02/nodes/myCellManager02/servers/dmgr/ server.xml#TransactionService_1,process=dmgr,platform=proxy, node=myCellManager02,j2eeType=JTAResource,J2EEServer=dmgr, version=6.1.0.19,type=TransactionService, mbeanIdentifier=/Program Files/IBM/WebSphere/AppServer/profiles/ Dmgr01/config/cells/myCell02/nodes/myCellManager02/servers/dmgr/ server.xml#TransactionService_1,cell=myCell02,spec=1.0" instead of the expected: "WebSphere:name=cells/myCell02/nodes/myCellManager02/servers/ dmgr/server.xml#TransactionService_1,process=dmgr, platform=proxy,node=myCellManager02,j2eeType=JTAResource, J2EEServer=dmgr,version=6.1.0.19,type=TransactionService, mbeanIdentifier=cells/myCell02/nodes/myCellManager02/servers/ dmgr/server.xml#TransactionService_1,cell=myCell02,spec=1.0" PROBLEM CONCLUSION:? The code has been modified to check for '%20' in the ObjectName and replace with a Space. The fix for this APAR is currently targeted for inclusion in fix pack 6.0.2.31 and 6.1.0.19. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg2700498 Note that both PK54440 and this APAR, PK69471 will be included in fix pack 6.1.0.19. Therefore, there will be no error included the V6.1 fix pack stream. Directions to apply fix: Fix applies to Editions: Release: 6.0 6.1 _x_ ___ Application Server (Express or Base) _x_ ___ 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 X_ 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.7 or later 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=swg24012718 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) For WebSphere Application Server versions 6.0.2.25 through 6.0.2.31 copy 6.0.2.25-WS-WAS-IFPK69471.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 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.0.2.25-WS-WAS-IFPK69471.pak) 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 WebSphere 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 (6.0.2.25-WS-WAS-IFPK69471.pak). 6) Uninstall the maintenance package. 7) Restart WebSphere. Directions to re-apply fix: 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: