Fix (APAR): PM63290 Status: Fix Release: 7.0.0.23,7.0.0.21,7.0.0.19,7.0.0.17,7.0.0.15,7.0.0.13,7.0.0.11 Operating System: AIX,HP-UX,IBM i,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PM63290 Byte size of APAR: 52077 Date: 2012-06-14 Abstract: The NumberFormat parse function can return an incorrect value for a decimal number. Description/symptom of problem: PM63290 resolves the following problem: ERROR DESCRIPTION: Abstract: com.ibm.icu.text.DecimalFormat.clone creates decimal format instances which operate incorrectly in multi-threaded scenarios. (See ICU ticket #5358.) Description: When new instances of com.ibm.icu.text.DecimalFormat are created using DecimalFormat.clone() the new instance shares state with the initial DecimalFormat instance. As a result, use of the initial instance in a first thread is not safe with the concurrent use of the new clone instance in a second thread. This problem was reported as ICU ticket #5358. For more information, see: http://bugs.icu-project.org/trac/ticket/5358 LOCAL FIX: NONE PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server v7.0 with applications using the ICU4J library PROBLEM DESCRIPTION: The NumberFormat parse function can return an incorrect value for a decimal number. RECOMMENDATION: None When parsing a decimal number, NumberFormat can intermittently return an incorrect result which will cause the application to process with an invalid value. The DecimalFormat clone method does not create a new DigitList object for each new DecimalFormat instance, resulting in multiple instances of DecimalFormat sharing the same DigitList. If multiple threads enter parsing simultaneously, this can cause the result on one thread to be corrupted by processing on another thread. PROBLEM CONCLUSION: DecimalFormat has been updated to prevent cross thread corruption. This error will not occur on WebSphere Application Server V8.0 and later due to its use of a later version of ICU4J. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.25. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: Fix applies to Editions: Release 7.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) __ Edge Components __ Developer 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.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into the maintenance directory. 2) Shutdown WebSphere Application Server. Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 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 Application Server. Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * 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 Application Server. 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 Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server. Additional Information: