Fix (APAR): PK71773 Status: Fix Release: 7.0 Operating System: AIX,HP-UX,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: 548052 Byte size of APAR: 197284293 Date: 2008-09-25 Abstract: Provides several fixes to the Java SDK Description/symptom of problem: PK71773 resolves the following problem: ERROR DESCRIPTION:? This APAR is an iFIX for JAVA Software Developer Kit LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: All users of WebSphere Application Server PROBLEM DESCRIPTION: Provides several fixes to the Java SDK RECOMMENDATION: None This fixes multiple problems in the Java SDK that ships with WAS 7.0.0.0. PROBLEM CONCLUSION:? - The ikeyman tool will throw an error while using restricted policy files and creating a p12 file. Opening existing p12 files works, but creating a new one causes an error to occur stating "The command cannot complete because your JRE is using restricted policy files.". - In rare cases a memory allocation error can occur while running a server with verbose:gc enabled. Depending on the value of the MALLOC_CHECK_ environment variable, an error message may be displayed to stderr stating "*** glibc detected *** /opt/IBM/WebSphere/AppServer/java/bin/java: double free or corruption (!prev): 0x00002aaab5cfe9b0 **", followed by a backtrace. This can cause the server startup process to hang. - While performing certain actions, like accessing the "Service client policy set bindings" panel of the Administrative Console, the server process will crash, and a javacore and core dump will be generated. This is caused by a segmentation error in the VM's just-in-time compiler. The native_stderr.log file will contain details of the crash and show that it's occurring in j9jit24.dll or libj9jit24.so. This only happens on Windows, Linux, and AIX platforms. - A bug in the java.beans.XMLEncoder class can cause JavaBeans to be serialized incorrectly and lead to missing information when the JavaBeans are populated with the java.beans.XMLDecoder. This only affects the Windows, Linux, and AIX platforms. This doesn't cause any known problems in the core WAS product, but it can cause problems for customer applications or stack products that make use of the XMLEncoder. - (HPUX Only) EJB objects are incorrectly generated during deployment which can lead to a java.lang.ClassCastException at runtime. The error message will look something like java.lang.ClassCastException:$Proxy31 cannot be cast to suite.r50.base.acc20.EJSRemoteCMPAITestCMPHome_ed49d0b1. - (HPUX Only) The wsgen tool can fail on HP can fail with a NullPointerException. The error looks like "java.lang.NullPointerException at com.sun.tools.internal.ws.processor.modeler.annotation.WebServic eAP.isSubtype(WebServiceAP.java:345)". The fix for this APAR is currently targeted for inclusion in the SDK SR3 Fixpack. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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-1.ibm.com/support/docview.wss?rs=180&uid=swg24020212 1) The fix is delivered as a single file with a .pak extension (such as 7.0.0.1-WS-WAS-IFPK12345.pak). Copy the .pak file directly to the maintenance directory, /maintenance. 2) Shutdown WebSphere 3) For IBM i users, use the update command to install and uninstall the interim fix. The IBM Information Center can provide additional details, if needed, on the use of this command. http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update. For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. To determine why some maintenance packages have been identified as not applicable, see description in log found in /logs/tmp*/updatelogs.txt 8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 9) Restart WebSphere Directions to remove fix: 1) Shutdown WebSphere 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) Select 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: