Fix (APAR): PK33460 Status: Fix Release: 6.0.2 Operating System: AIX Supersedes Fixes: CMVC Defect: 397177 Byte size of APAR: 10692 Date: 2006-10-26 Abstract: Native libraries for node capability detection were not being loaded properly by Extended Deployment on the 64 bit AIX platform. Description/symptom of problem: PK33460 resolves the following problem: ERROR DESCRIPTION: When the incoming traffic to the On Demand Routers increases, the number of running application servers is not increased proportionally when the dynamic cluster is running in automatic mode. At the same time, the following error message may be seen in the SystemOut logs: ASND0005E: Unable to obtain information on processor speed. This problem is seen specifically on the 64 bit AIX platform when running WebSphere Extended Deployment version 6.0.2. The inability of the Placement component to not behave as designed is caused because it cannot detect node capabilities of the host(s) running on the AIX hardware that has additional servers configured on it. LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Extended Deployment v6.0.2, and v6.0.2 over Network Deployment 61 using a deployment on AIX 64 bit arch. PROBLEM DESCRIPTION: Native libraries for node capability detection were not being loaded properly by Extended Deployment on the 64 bit AIX platform. RECOMMENDATION: None WebSphere Extended Deployment is unable to load the native nodedetect library correctly on 64 bit AIX architecture. Alongside this failure, it prints out a message with the following text to the SystemOut.log - "ASND0005E: Unable to obtain information on processor speed". Since WebSphere Extended Deployment is unable to determine node capabilities correctly, this results in erroneous decision making on behalf of the Application Placement Controller as also the Dynamic workload management controller. This results in application servers not being started up when additional traffic is received by the system, and existing traffic also may not be balanced across available application servers. PROBLEM CONCLUSION: This fix addresses the problem with loading the native nodedetect library on AIX 5.3+ 64 bit architecture. This fix can be installed on WebSphere Extended Deployment 6.0.2 and WebSphere Extended Deployment 6.0.2 over Network Deployment 6.1. 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 __ 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.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. 1) Copy PKxxxxx.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 (PKxxxxx.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 (PKxxxxx.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: